6 Commits (549edcabb644dfe3b8a19701be28f0499a7d3d59)

Author	SHA1	Message	Date
Onder Kalaci	549edcabb6	Allow disabling node(s) when multiple failures happen ... As of master branch, Citus does all the modifications to replicated tables (e.g., reference tables and distributed tables with replication factor > 1), via 2PC and avoids any shardstate=3. As a side-effect of those changes, handling node failures for replicated tables change. With this PR, when one (or multiple) node failures happen, the users would see query errors on modifications. If the problem is intermitant, that's OK, once the node failure(s) recover by themselves, the modification queries would succeed. If the node failure(s) are permenant, the users should call `SELECT citus_disable_node(...)` to disable the node. As soon as the node is disabled, modification would start to succeed. However, now the old node gets behind. It means that, when the node is up again, the placements should be re-created on the node. First, use `SELECT citus_activate_node()`. Then, use `SELECT replicate_table_shards(...)` to replicate the missing placements on the re-activated node.	2021-12-01 10:19:48 +01:00
Onder Kalaci	38b08ebde9	Generalize the error checks while removing node ... The checks for preventing to remove a node are very much reference table centric. We are soon going to add the same checks for replicated tables. So, make the checks generic such that: (a) replicated tables fit naturally (b) we can the same checks in `citus_disable_node`.	2021-11-26 14:25:29 +01:00
Hadi Moshayedi	dda53a0bba	GUC for replicate reference tables on activate.	2020-04-08 12:42:45 -07:00
Marco Slot	924cd7343a	Defer reference table replication to shard creation time	2020-04-08 12:41:36 -07:00
Philip Dubé	c563e0825c	Strip trailing whitespace and add final newline (#3186) ... This brings files in line with our editorconfig file	2019-11-21 14:25:37 +01:00
Murat Tuncer	a837dde1a0	Add failure tests for master add/remove/disable/active node	2018-07-13 18:06:24 +03:00