elasticsearch setup by mahara causes Elasticsearch Server status to go from green to yellow

Bug #1265629 reported by Robert Lyon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Fix Released
High
Unassigned

Bug Description

When I have a newly installed Elasticsearch Server I can check it's health with:

curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'

and shows status as 'green'

but when I enable elasticsearch in mahara the status changes to 'yellow' and there are unassigned shards

we might need to have a setting in mahara to deal with non distributed (localhost) elasticsearch setups where it makes more sense to have only one shard.

In the /etc/elasticsearch/elasticsearch.yml file it says:

# Note, that for development on a local machine, with small indices, it usually
# makes sense to "disable" the distributed features:
#
# index.number_of_shards: 1
# index.number_of_replicas: 0

Revision history for this message
Robert Lyon (robertl-9) wrote :

have added patch to make the mahara elasticsearch respect the settings of the ElasticSearch Server for the shards/replicas
https://reviews.mahara.org/#/c/2865/

Changed in mahara:
status: Confirmed → In Progress
Revision history for this message
Mahara Bot (dev-mahara) wrote : A change has been merged

Reviewed: https://reviews.mahara.org/2865
Committed: http://gitorious.org/mahara/mahara/commit/f1139ed4a50c74e33c0b07085dd9f4ad2e6a1c9d
Submitter: Aaron Wells (<email address hidden>)
Branch: master

commit f1139ed4a50c74e33c0b07085dd9f4ad2e6a1c9d
Author: Robert Lyon <email address hidden>
Date: Mon Jan 6 12:28:32 2014 +1300

Elasticsearch setting of shards/replicas causing problems (Bug #1265629)

Need to let mahara elasticsearch respect the shards/replicas settings
set in ElasticSearch server

Change-Id: Idafcb87ebf1d01f97b2671a3eeee9c6d15a60093
Signed-off-by: Robert Lyon <email address hidden>

Aaron Wells (u-aaronw)
Changed in mahara:
status: In Progress → Fix Committed
Robert Lyon (robertl-9)
Changed in mahara:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.