Elasticsearch cluster restarts are slowed down because of writers which do not respect the "frozen writes". We have not much idea of which they are, so we should dress a list of the writes we see occurring on the cluster during freezes and track them (by index written, user agent, source IP, whatever...).
Description
Description
Event Timeline
Comment Actions
Randomly thinking about this, it seems the most obvious way would be to have clients send appropriate user agent's in the http requests, and track the set of unique user agents and their request rates. If the user agents are fairly obvious we should be able to see what is doing what, and be able to ask for user agents to be clarified where necessary.
Comment Actions
Closing out low/est priority tasks over 6 months old with no activity within last 6 months in order to clean out the backlog of tickets we will not be addressing in the near term. Please feel free to reopen if you think a ticket is important, but bare in mind that given current priorities and resourcing, it is unlikely for the Search team to pick up these tasks for the indefinite future. We hope that the requested changes have either been addressed by or made irrelevant by work the team has done or is doing -- e.g. upgrading Elasticsearch to a newer version will solve various ES-related problems -- or will be subsumed by future work in a more generalized way.
Comment Actions
Re-opening tasks and removing from team workboard per IRC feedback given yesterday and discussion with MPham.