git-hulk opened a new pull request, #3545: URL: https://github.com/apache/kvrocks/pull/3545
After a slot has been migrated away, the source node keeps `forbidden_slot_range_` set. That is normally harmless because the topology no longer routes the slot to this node, so the forbidden-slot check is never reached. But `CLUSTER RESET` clears the topology while leaving the migrator's forbidden range intact — a subsequent SETNODES that reassigns the slot back to this node then spuriously rejects writes with `TRYAGAIN Can't write to slot being migrated`. Explicitly release the forbidden slot range in `Cluster::Reset` to fix this. Assistant-By: Claude Opus 4.7 -- 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]
