Page MenuHomePhabricator

Remove row/rack awareness in Elasticsearch config
Closed, DeclinedPublic


As we prepare for several Elasticsearch upgrades, we've noticed that the row/rack awareness as currently configured in our puppet can cause issues during upgrade operations.

Since this adds significant complexity to shard allocation and we have a DR strategy that does not require it, we need to review this configuration and decide whether or not to keep it.

Event Timeline

Per conversation with @Gehel , removing row/rack awareness introduces too much risk of data loss. We need to revisit this at some point, but for now we have decided to address Elasticsearch's refusal to move shards in other ways: capacity , shard sizes, etc.