You can see this is exactly the case - you have a single node and Elasticsearch won't assign primary shard and replicas of it on the same node. If you would run a second node Elasticsearch would allocate that 15 unassigned shards and rebalance the shards between the two node cluster - try that out, even locally.
Of course, if you are using that single node for development you can just remove the replicas by running:
curl -XPUT 'localhost:9200/_settings' -d '{"index" : { "number_of_replicas" : 0 }}'
However remember that in production you usually don't want to have primaries and their replicas on the same node and you want more than a single Elasticsearch node running.
--
Regards,
Rafał Kuć
Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/
| Health of cluster: yellow (35 50) curl -XGET 'localhost:9200/_cluster/health?pretty' { "cluster_name": "elasticsearch", "status": "yellow", "timed_out": false, "number_of_nodes": 1, "number_of_data_nodes": 1, "active_primary_shards": 35, "active_shards": 35, "relocating_shards": 0, "initializing_shards": 0, "unassigned_shards": 15 } -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b7d49cbb-687f-4eac-8b54-9b5b24c886db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1295114784.20140710155719%40alud.com.pl.
For more options, visit https://groups.google.com/d/optout.
