Doing a thorough job of deleting all indexes got my installation back to
status yellow, apparently fully functional when I re-established my test
index with a new name. Sledgehammer, but I didn't need to sow the ground
with salt.
On Friday, November 21, 2014 11:21:26 AM UTC-8, Pitaga wrote:
You can get it to green if you get rid of the replicas - curl -XPUT
localhost:9200/*/_settings -d '{ index : { number_of_replicas : 0 } }'
On 26 November 2014 at 09:36, Pitaga ach...@blarg.net wrote:
Doing a thorough job of deleting all indexes got my installation back to
status yellow,
Just a wild guess, but it seems that the /etc/init.d/elasticsearch restart
command will, if properly named, stop a currently running instance and then
start it.
If you issue the curl _shutdown command and then the restart command
directly after without any delays, then perhaps that double blow
Brian, thanks for the help on correcting what I've been doing. Once I get
my system unwedged, I won't mix curl commands and scripts.
I deleted the one remaining index that I had established, and then all the
remaining .marvel indexes. Then I re-established mapping and settings for
my index.
You have 7 unassigned shards. Are you sure you always had one node in the
cluster?
It seems there were once more than one nodes. So start two (or more) nodes
on your laptop and the cluster state will get green.
Note, on single node, always create with replica level 0. The default is 1,
which has
Thanks, Joerg.
bin/elasticsearch -Des.node.data=true -Des.de.master=false
-Des.node.name=DataOne
and
curl -XPUT 'localhost:9200/testindex2/_settings' -d ' {index :
{number_of_replicas : 0}}'
with several restarts, have got me to a state where I see the following
command-response
When I shutdown and restart Elasticsearch on my Ubuntu laptop, the status
is yellow until I attempt to open an index, at which time the status
changes to red. The output for
curl http://localhost:9200/_cluster/health?pretty=true;
is
{
cluster_name : elasticsearch,
status
