mirror of https://github.com/citusdata/citus.git
b5d384cb3e
Before this commit, we had: ```SQL SELECT citus_disable_node(nodename, nodeport, force boolean DEFAULT false) ``` Where, we allow forcing to disable first worker node with `force:=true`. However, it entails the risk for losing data / diverging placement data etc. With `force` flag, we control disabling the first worker node, and with `async` flag we control whether the changes are done via bg worker or immediately. ```SQL SELECT citus_disable_node(nodename, nodeport, force boolean DEFAULT false, sync boolean DEFAULT false) ``` Where we can achieve all the following: | Mode | Data loss possibility | Can run in 2PC | Handle multiple node failures | Immediately effective | | --- |--- |--- |--- |--- | | force:false, sync: false | false | true | true | false | | force:false, sync: true | false | false | false | true | | force:true, sync: false | true | true | true | false | | force:true, sync: true | false | false | false | true | |
||
|---|---|---|
| .. | ||
| hammerdb | ||
| recovery | ||
| regress | ||