Change Details

There is currently a plan in the works for mutli-dc oriented search. This is primarily tracked in {T105703} The plan as it stands now is to use the jobqueue system to update two unrelated clusters in order to maintain parity. Roughly speaking we plan on using our newfound redundancy to tweak various parameters in ES and to allow upgrades to be less user impacting. This is all related to a larger RFC as well https://phabricator.wikimedia.org/T88666. The apifeatureusage extension seems to bypass the normal processing pipeline for Elasticsearch events which in this case will mean it cannot survive the multi-dc mode. At the moment, during maintenance it is a generally understand process to leave only apifeatureusage in write mode for this reason.

There is currently a plan in the works for multi-dc oriented search. This is primarily tracked in {T105703} The plan as it stands now is to use the jobqueue system to update two unrelated clusters in order to maintain parity. Roughly speaking we plan on using our newfound redundancy to tweak various parameters in ES and to allow upgrades to be less user impacting. This is all related to a larger RFC as well https://phabricator.wikimedia.org/T88666. The apifeatureusage extension seems to bypass the normal processing pipeline for Elasticsearch events which in this case will mean it cannot survive the multi-dc mode. At the moment, during maintenance it is a generally understood process to leave only apifeatureusage in write mode for this reason.

There is currently a plan in the works for mutlmulti-dc oriented search. This is primarily tracked in {T105703} The plan as it stands now is to use the jobqueue system to update two unrelated clusters in order to maintain parity. Roughly speaking we plan on using our newfound redundancy to tweak various parameters in ES and to allow upgrades to be less user impacting. This is all related to a larger RFC as well https://phabricator.wikimedia.org/T88666. The apifeatureusage extension seems to bypass the normal processing pipeline for Elasticsearch events which in this case will mean it cannot survive the multi-dc mode. At the moment, during maintenance it is a generally understandood process to leave only apifeatureusage in write mode for this reason.