jenkins-bot has submitted this change and it was merged. Change subject: Add comments about Elasticsearch prod config ......................................................................
Add comments about Elasticsearch prod config We have some opinions on the right way to set up Elasticsearch for CirrusSearch so we should make those public in the README. Bug: 56165 Change-Id: I4f960684ad8412bb752d155ae49f7af17afb20c3 --- M README 1 file changed, 44 insertions(+), 0 deletions(-) Approvals: Chad: Looks good to me, approved jenkins-bot: Verified diff --git a/README b/README index d59164e..760dd5e 100644 --- a/README +++ b/README @@ -130,6 +130,50 @@ The safest thing if you don't know what is required for your update is to execute (1.B). + +Production suggestions +---------------------- + +Elasticsearch + +All the general rules for making Elasticsearch production ready apply here. So you don't have to go +round them up below is a list. Some of these steps are obvious, others will take some research. +1. Have >= 3 nodes. +2. Configure Elasticsearch for memlock. +3. Change each node's elasticsearch.yml file in a few ways. +3a. Change node name to the real host name. +3b. Turn off autocreation and some other scary stuff by adding this (tested with 0.90.4): + ################################### Actions ################################# + ## Modulo some small changes to comments this section comes directly from the + ## wonderful Elasticsearch mailing list, specifically Dan Everton. + ## + # Require explicit index creation. ES never autocreates the indexes the way we + # like them. + ## + action.auto_create_index: false + + ## + # Protect against accidental close/delete operations on all indices. You can + # still close/delete individual indices. + ## + action.disable_close_all_indices: true + action.disable_delete_all_indices: true + + ## + # Disable ability to shutdown nodes via REST API. + ## + action.disable_shutdown: true + + +CirrusSearch + +You should change the number of replicas to at least one, two if you want protection from crashes +during upgrades. More replicas will help distribute queries across more nodes. Having more +replicas than nodes doesn't make sense and Elasticsearch will stay "yellow" if you do that. +Anyway, you should add this to LocalSettings.php to change it: + $wgCirrusSearchContentReplicaCount = array( 'content' => 2, 'general' => 2 ); + + Licensing information --------------------- CirrusSearch makes use of the Elastica library to connect to elasticsearch <http://elastica.io/>. -- To view, visit https://gerrit.wikimedia.org/r/91983 To unsubscribe, visit https://gerrit.wikimedia.org/r/settings Gerrit-MessageType: merged Gerrit-Change-Id: I4f960684ad8412bb752d155ae49f7af17afb20c3 Gerrit-PatchSet: 1 Gerrit-Project: mediawiki/extensions/CirrusSearch Gerrit-Branch: master Gerrit-Owner: Manybubbles <[email protected]> Gerrit-Reviewer: Chad <[email protected]> Gerrit-Reviewer: jenkins-bot _______________________________________________ MediaWiki-commits mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-commits
