Unfortunately there is nothing in the logs about the issue.
Here is the hardware:
[image: Inline image 1]
The ES version is 1.4.0 , when I reduce the number of replicas to 0, it
would became green.
Here
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/states.html
the next is stated:
If a shard cannot be assigned, for example you’ve overallocated the number
of replicas for the number of nodes in the cluster, they will remain
UNASSIGNED.
How can I understand the real reason of unassigning the shards?
According to the bigdesk - the nodes are feeling themselves very good,
there are no queues and enough of the resources.
[image: Inline image 2]
I think that my hardware can hold more then 5 nodes. I've tried once to
reduce them to 10, but during the index creation some were still unassigned.
However, when I do restart of some node - it could be that every would be
assigned after the shards relocation process.
Regards,
On Tue, Nov 18, 2014 at 11:26 AM, Mark Walkom markwalkom@gmail.com wrote:
Your logic around having so many shards may make sense, but you still end
up having to move the same amount of data and it's more over head.
You should have N number of shards, where N is the number of nodes.
Check your logs, there may be something in there. Otherwise can you
provide more details on your node size; RAM, disk, CPU, ES and java
version, that sort of thing,
On 18 November 2014 19:59, Pavel P pavel@kredito.de wrote:
Hi again,
The question is still actual.
Yesterday I've updated the ES version to 1.4.0, in the night new index
was created, currently it is not able to assign 2 nodes:
https://lh5.googleusercontent.com/-e5DZN7BvA3w/VGsKW-0Su2I/AAAAAAAAAKo/lrst5q10vWI/s1600/Screen%2BShot%2B2014-11-18%2Bat%2B10.58.37%2BAM.png
Please, advice me something 
On Monday, November 17, 2014 11:02:43 AM UTC+2, Pavel P wrote:
Hi,
I have a cluster from 5 nodes, where I store the information from the
logstash.
Recently I've tried to increase the number of shards in the logstash
index to 20 (from 5).
From the beginning everything went well, all the shards were allocated
and the cluster state was green.
But, currently, when the new index is started (at the beginning of the
day), I met the situation when some shards are not allocated:
https://lh3.googleusercontent.com/-R3bWkXbXCbU/VGmwngnPOzI/AAAAAAAAAKY/9n8XlVCGPyc/s1600/Screen%2BShot%2B2014-11-17%2Bat%2B10.23.04%2BAM.png
Nothing happens during the day, while I thing the cluster has resources.
If I would restart some nodes from the cluster, it could turn out that
all the shards would be allocated.
The idea which I'm trying to reach - more shards => each shard is
smaller => it would allocate them faster, it would index faster, because of
the indexing on each shard.
Questions:
- Why it is not able to allocate those shards during the index creation?
- Why it does not allocate those shards during the day?
- What is the recommended shards number for N nodes?
Any thoughts are welcome.
Regards,
--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/6b9b0a09-c6b3-428d-ae26-148e94480a16%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/6b9b0a09-c6b3-428d-ae26-148e94480a16%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/q5Xkn9pc9EM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZkmUcML7MGPvf_93xVhVsQR4X5iETUpquDbmkFpo3nMXw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZkmUcML7MGPvf_93xVhVsQR4X5iETUpquDbmkFpo3nMXw%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
Pavel Polyakov
Software Engineer - PHP
E-mail: pavel@kredito.de
Skype: pavel.polyakov.x1
https://www.facebook.com/kreditech
Kreditech Holding SSL GmbH
Am Sandtorkai 50, 20457 Hamburg, Germany
Office phone: +49 (0)40 - 605905-60
Authorized representatives: Sebastian Diemer, Alexander Graubner-Müller
Company registration: Hamburg HRB122027
facebook.com/kreditech https://www.facebook.com/kreditech
https://www.facebook.com/kreditech
This e-mail contains confidential and/or legally protected information. If
you are not the intended recipient or if you have received this e-mail by
error please notify the sender immediately and destroy this e-mail. Any
unauthorized review, copying, disclosure or distribution of the material in
this e-mail is strictly forbidden. The contents of this e-mail is legally
binding only if it is confirmed by letter or fax. The sending of e-mails to
us does not have any period-protecting effect. Thank you for your
cooperation.
--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAFVUaqNLQs05aONd8dOWcM4GWh1K8kKk-Ec6iMopCYwxaS%2BLtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
