In CnosDB After move vnode, compact vnode report vnode not found

Question

version cnosdb 2.4.0, revision 6776285b45d1441cff5896a345b45f4f03b85522

//first move vnode

public > move vnode 7 to node 2001;

Query took 3.655 seconds.

---

//then compact the vnode

public > compact vnode 7;

422 Unprocessable Entity, details: {"error_code":"050015", "error_message": "vnode not found: 7"}

Answer 1

In CnosDB-2.4, the move vnode command causes the new vnode to have a different id than the original vnode. This is because in CnosDB-2.4, vnode replica groups use the raft protocol to ensure consistency between them, so the way to implement move vnode becomes: first add a new vnode as a member of that replica group to the target node, and then remove the vnode that was moved. This usually results in the new vnode having a different id than the original vnode.