mirror of https://github.com/citusdata/citus.git
549edcabb6
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. |
||
|---|---|---|
| .. | ||
| columnar_copyto.source | ||
| columnar_data_types.source | ||
| columnar_load.source | ||
| hyperscale_tutorial.source | ||
| multi_agg_distinct.source | ||
| multi_agg_type_conversion.source | ||
| multi_alter_table_statements.source | ||
| multi_behavioral_analytics_create_table.source | ||
| multi_behavioral_analytics_create_table_superuser.source | ||
| multi_complex_count_distinct.source | ||
| multi_copy.source | ||
| multi_load_data.source | ||
| multi_load_data_superuser.source | ||
| multi_load_more_data.source | ||
| multi_mx_copy_data.source | ||
| multi_outer_join.source | ||
| multi_outer_join_reference.source | ||
| tablespace.source | ||
| worker_copy.source | ||