I got a problem of many "unassigned shards". So through some reading I tryed to do : index.routing.allocation.disable_allocation= false
This returned me:
index.routing.allocation.disable_allocation please check that any required plugins are installed
Looking around I didnt find such plugins. Also I didnt yet see a reference in ES 5.X for "index.routing.allocation.disable_allocation". Is there such an option in ES 5.2?
If no, what should I do?
Also if someone knows from what can this problem can happen, and what other solutions are there?
I dont know why, the machines that I am working on are not from our company but an outside one. From my understanding they copied the VM of the ES a few times, and copied the VMs of from where the filebeats sends the logs to ES
What logs?
I actualy don't understand enough in shards. So I can't answer the 3rd question.
When looking at the logs of logstash, I get:
error: "failed to derive xcontent" (but I am not sure this is connected)
(Thanks on the quick reply)
Since the machine I am working on is secure I cant copy paste from there or work with internet therefore I will not copy but type in the releavent parts:
I got a bunch of numbers then KppASWN
and then I got:
51 UNASSIGNED
So if I open a new ElasticSearch instance (which opens a new node) this will fix the problem?
A few questions regarding this:
1- how to erase replicas?
2 - how did this happen how did replicas come upon?
3 - how opening a new node will solve it, does ES know how to allocate shards automatically?
Replica's are added by default and will be automatically assigned by ES if you add more nodes to the cluster.
You can dynamically change the number of replicas using something like; curl -XPUT localhost:9200/*/_settings -d '{ "index" : { "number_of_replicas" : 0 } }'.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.