Search code examples
databasecnosdb

After the node goes offline, data is still being written to the offline node

I am trying the node offline function here. But I encountered a problem during the process：After the node goes offline, data is still being written to the offline node.

the step as follow:

  1. start cluster 3m2d;

  2. wait a minute ,check usage_schema data which node stored the vnode;

  3. removenode the nodeid;

  4. wait a minute;Check whether the usage_schema data has increased, and check whether another node has a new vnode.

Has anyone encountered this problem? Can you help explain it?

Solution

  • According to the official documentation, the cnosdb cluster will remove the specified node from the cluster through the REMOVENODE command. If the force option is added, the existing data in the node will be migrated to other available nodes. If there is no force option, the node will retain the existing bucket and will not create a new bucket. So the situation you mentioned will occur.