This thread identified two improvements to scanning CME we would like to address:
Suggested command:
CSCAN <cluster cursor> <node cursor> [MATCH pattern] [COUNT count] [TYPE type]
The command does an incremental scan of cluster, using moved requests to indicate when the client has finished parsing the requests on the given node. If the command is sent to the wrong node, it will automatically be redirected to the correct one. The scan will guarantee that all data at the start and end of the scan will still hit at least once.
The command will allow use cases that allow external third parties to slowly scan the entire cluster, handling cases where slots may have moved during the course of the migration.
This thread identified two improvements to scanning CME we would like to address:
Suggested command:
CSCAN <cluster cursor> <node cursor> [MATCH pattern] [COUNT count] [TYPE type]The command does an incremental scan of cluster, using moved requests to indicate when the client has finished parsing the requests on the given node. If the command is sent to the wrong node, it will automatically be redirected to the correct one. The scan will guarantee that all data at the start and end of the scan will still hit at least once.
The command will allow use cases that allow external third parties to slowly scan the entire cluster, handling cases where slots may have moved during the course of the migration.