Shards not replicating to two nodes

I have a new elasticsearch cluster with 4 nodes and for some reason I can't
get the shards distributed across all of these. Shards are only being
copied to 2/4 rather than all of them which is what I'm after.

The config is the same on each:

cluster.name: elasticsearch
node.name: "xxxxx"
gateway.expected_nodes: 4
discovery.zen.minimum_master_nodes: 3
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["1.1.1.1", "1.1.1.2", "1.1.1.3"]

The rest is default. Any thoughts?

https://lh3.googleusercontent.com/-Cl8e-SyNVao/VLj6G0wHHrI/AAAAAAAAASU/-QxhgWUoC3Q/s1600/ScreenHunter_353%2BJan.%2B16%2B11.44.jpg

--
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/9ce6e841-2a03-46be-8e63-3590f752d6bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi ,

Can you check the following -

  1. Disk space on the machine where shards are not getting used.
  2. See the configuration of the node in those machines. See if the
    client node only config is enabled in the config.

Thanks
Vineeth

On Fri, Jan 16, 2015 at 5:20 PM, Stewart Gray stewart.gray@gmail.com
wrote:

I have a new elasticsearch cluster with 4 nodes and for some reason I
can't get the shards distributed across all of these. Shards are only being
copied to 2/4 rather than all of them which is what I'm after.

The config is the same on each:

cluster.name: elasticsearch
node.name: "xxxxx"
gateway.expected_nodes: 4
discovery.zen.minimum_master_nodes: 3
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["1.1.1.1", "1.1.1.2", "1.1.1.3"]

The rest is default. Any thoughts?

https://lh3.googleusercontent.com/-Cl8e-SyNVao/VLj6G0wHHrI/AAAAAAAAASU/-QxhgWUoC3Q/s1600/ScreenHunter_353%2BJan.%2B16%2B11.44.jpg

--
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/9ce6e841-2a03-46be-8e63-3590f752d6bf%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9ce6e841-2a03-46be-8e63-3590f752d6bf%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 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/CAGdPd5%3D-ba5OTVj5DNmx5vg7ubv%3Dsw3r96%3DZZR7fQG58fbbizg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi,

Plenty of disk space on the two machines not receiving shards - there is a
symbolic link from /var/lib/elasticsearch to a 400gb drive on each. If I
get logstash to log to elasticsearch on one of these, and remove it from
the cluster I see the indicies being created in the right place.

The configuration is exactly the same on all machines (apart from the
obvious stuff, node name, and other node IP addresses).

Cheers

On Friday, 16 January 2015 12:28:52 UTC, vineeth mohan wrote:

Hi ,

Can you check the following -

  1. Disk space on the machine where shards are not getting used.
  2. See the configuration of the node in those machines. See if the
    client node only config is enabled in the config.

Thanks
Vineeth

On Fri, Jan 16, 2015 at 5:20 PM, Stewart Gray <stewar...@gmail.com
<javascript:>> wrote:

I have a new elasticsearch cluster with 4 nodes and for some reason I
can't get the shards distributed across all of these. Shards are only being
copied to 2/4 rather than all of them which is what I'm after.

The config is the same on each:

cluster.name: elasticsearch
node.name: "xxxxx"
gateway.expected_nodes: 4
discovery.zen.minimum_master_nodes: 3
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["1.1.1.1", "1.1.1.2", "1.1.1.3"]

The rest is default. Any thoughts?

https://lh3.googleusercontent.com/-Cl8e-SyNVao/VLj6G0wHHrI/AAAAAAAAASU/-QxhgWUoC3Q/s1600/ScreenHunter_353%2BJan.%2B16%2B11.44.jpg

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/9ce6e841-2a03-46be-8e63-3590f752d6bf%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9ce6e841-2a03-46be-8e63-3590f752d6bf%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 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/6fd7093c-b48f-4a90-918b-5d06b5b2ffb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Turns out it was a versioning issue - we were running slightly different
versions of elasticsearch on the two not replicating. I upgraded these and
now it's working wonderfully.

Thanks for your help.

Cheers

On Friday, 16 January 2015 12:40:54 UTC, Stewart Gray wrote:

Hi,

Plenty of disk space on the two machines not receiving shards - there is a
symbolic link from /var/lib/elasticsearch to a 400gb drive on each. If I
get logstash to log to elasticsearch on one of these, and remove it from
the cluster I see the indicies being created in the right place.

The configuration is exactly the same on all machines (apart from the
obvious stuff, node name, and other node IP addresses).

Cheers

On Friday, 16 January 2015 12:28:52 UTC, vineeth mohan wrote:

Hi ,

Can you check the following -

  1. Disk space on the machine where shards are not getting used.
  2. See the configuration of the node in those machines. See if the
    client node only config is enabled in the config.

Thanks
Vineeth

On Fri, Jan 16, 2015 at 5:20 PM, Stewart Gray stewar...@gmail.com
wrote:

I have a new elasticsearch cluster with 4 nodes and for some reason I
can't get the shards distributed across all of these. Shards are only being
copied to 2/4 rather than all of them which is what I'm after.

The config is the same on each:

cluster.name: elasticsearch
node.name: "xxxxx"
gateway.expected_nodes: 4
discovery.zen.minimum_master_nodes: 3
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["1.1.1.1", "1.1.1.2", "1.1.1.3"]

The rest is default. Any thoughts?

https://lh3.googleusercontent.com/-Cl8e-SyNVao/VLj6G0wHHrI/AAAAAAAAASU/-QxhgWUoC3Q/s1600/ScreenHunter_353%2BJan.%2B16%2B11.44.jpg

--
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/9ce6e841-2a03-46be-8e63-3590f752d6bf%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9ce6e841-2a03-46be-8e63-3590f752d6bf%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 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/fc277656-5f8d-46c4-9cd0-057a9d2da630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.