RiversJin commented on PR #2829: URL: https://github.com/apache/kvrocks/pull/2829#issuecomment-2728066914
> can break the whole abandon range Yes. There‘s an implicit assumption here that only one migration task can exist for a shard at the same time. When a sub-range is being migrated back, it indicates the previous migration-out task has been completed and confirmed by the controller, making this approach valid. Of course, I noticed there‘s a TODO in the code about supporting concurrent migration tasks. Once this TODO is addressed, we'll need a different solution. By the way, I think assigning a unique ID to each migration task could help simplify the problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
