Data Redistribution
Data redistribution is done in the background and does not block ongoing operations when data is being transferred.
When the sending copyset completes its migration of data, it briefly delays live operations when assigning ownership to the new copyset. During this interval, transactions that were started during the migration process might fail, and iterator creation and query execution might fail. After this, there is a period of time where other processes (nodes and proxies) in the data grid begin to learn about the change in ownership of the data now at the new copyset so it is expected that operations occurring during that window can experience a timeout error at the client while the processes learn about the new configuration.
Statements and table listeners created before the data redistribution are out of date once the data redistribution is completed and receives an invalid resource error at the client. The object must be destroyed in the client application and re-created.