You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Information from Slack forum: "When you mark a chunk as stale, the chunk becomes under-replicated. When the failed data node becomes available then such chunks can be re-balanced using the copy_chunk API."
The text was updated successfully, but these errors were encountered:
icec102
changed the title
Obsolete restriction on RF=1: /api/latest/distributed-hypertables/create_distributed_hypertable/
Obsolete restriction on Replication factor = 1 still in the docs
Nov 20, 2023
Replication factor > 1 is now recommended, contrary to what the docs say.
Ref: /api/latest/distributed-hypertables/create_distributed_hypertable/
Docs: https://docs.timescale.com/api/latest/distributed-hypertables/create_distributed_hypertable/
Discussion: https://timescaledb.slack.com/archives/CPSD82EMU/p1700491915098979?thread_ts=1700220781.353329&cid=CPSD82EMU
Information from Slack forum: "When you mark a chunk as stale, the chunk becomes under-replicated. When the failed data node becomes available then such chunks can be re-balanced using the copy_chunk API."
The text was updated successfully, but these errors were encountered: