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.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T248925 Make MediaWiki release tarball compatible with PHP 8.0 | |||
| Resolved | Jdforrester-WMF | T300463 Make PHP 8.0 voting on MW master | |||
| Resolved | None | T283275 Make MW master tests pass on PHP 8.0 | |||
| Resolved | Reedy | T268861 CirrusSearch uses Elastica's Match class | |||
| Resolved | Reedy | T268863 Translate uses Elastica's Match class | |||
| Resolved | matthiasmullie | T268866 WikibaseMediaInfo uses Elastica's Match class | |||
| Invalid | None | T268864 WikibaseCirrusSearch uses Elastica's Match class | |||
| Resolved | Reedy | T268865 WikibaseLexemeCirrusSearch uses Elastica's Match class | |||
| Resolved | EBernhardson | T271777 Bump rufin/elastica (and related libraries) to versions that support PHP 8.0 | |||
| Resolved | Gehel | T263142 [EPIC] Upgrade Elasticsearch to version 7.10 | |||
| Declined | None | T304569 Remove row/rack awareness in Elasticsearch config |
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.