01-Dnode¶
¶
Dnode alter
1. Start only one dnode
2. Modify the monitor and debugflag parameters of the online dnode
3. Modify parameters of an offline dnode (error expected)
¶
Dnode create
1. Create dnode2
2. Check system tables such as ins_dnodes and ins_mnodes
3. Create database tables on these two dnodes and perform basic write and query operations
¶
Dnode drop force unsafe
1. Create 5 dnodes, establish a three-replica database on them, and write data
2. Create three mnodes
3. Stop one dnode and verify that it cannot be deleted
4. Use drop dnode force unsafe to forcibly delete this dnode
¶
Drop drop with mnode
Drop the dnode containing the mnode
¶
Dnode drop with replca-1 vnodes
Drop the dnode containing a single-replica vnode, and test the integrity of the data after vnode migration.
¶
Dnode drop with replca-3 vnodes
Drop the dnode containing a three-replica vnode, and test the integrity of the data after vnode migration.
¶
Drop drop with qnode and snode
Drop the dnode containing the mnode and snode
¶
Dnode drop with replca-1 vnode
Drop the dnode containing a single-replica vnode, and test the integrity of the data after vnode migration.
¶
Dnode drop with replca-3 vnode
Drop the dnode containing a three-replica vnode, and test the integrity of the data after vnode migration.
¶
Dnode check offline reason
Check whether the offline_reason field of the offline dnode is correct.
¶
Drop reuse dropped dnode
Check whether it is possible to repeatedly create and delete dnodes with the same FQDN.