mahara-contributors team mailing list archive

[Mahara Bot <1265629@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2865
Committed: http://gitorious.org/mahara/mahara/commit/f1139ed4a50c74e33c0b07085dd9f4ad2e6a1c9d
Submitter: Aaron Wells (aaronw@xxxxxxxxxxxxxxx)
Branch:    master

commit f1139ed4a50c74e33c0b07085dd9f4ad2e6a1c9d
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
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 <robertl@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1265629

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

Status in Mahara ePortfolio:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1265629/+subscriptions