Last modified: 2014-03-13 15:11:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T54277, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52277 - Add monitoring for Solr
Add monitoring for Solr
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-30 14:11 UTC by Siebrand Mazeland
Modified: 2014-03-13 15:11 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Siebrand Mazeland 2013-07-30 14:11:32 UTC
A lack of monitoring on Solr could cause bug 52148 to go unnoticed for a while (about a week).

This issue aims to have Solr monitored in such a way that "unexpected behaviour" would be noticed automatically, and <relevant roles> would be notified, so that service outages would be detected sooner and can be responded to quicker.
Comment 1 Niklas Laxström 2013-07-31 08:43:01 UTC
I was thinking whether we can have monitors that check the number of documents in the index, and alert if that drops a lot?
Comment 2 Andre Klapper 2014-03-13 13:10:38 UTC
Elasticsearch won over Solr (see https://www.mediawiki.org/wiki/Search#Solr_vs_Elasticsearch ) so this is INVALID now.
Elasticsearch monitoring is covered by bug 57210.
Comment 3 Niklas Laxström 2014-03-13 14:44:12 UTC
Andre: this is about TTMServer, which is still using Solr.

However, since we will be working migration to ElasticSearch for TTMServer, it makes no point to work on this bug.
Comment 4 Andre Klapper 2014-03-13 15:10:58 UTC
Uhm, thanks for clarifying. Wasn't aware of that from the bug description. :(

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links