Elastic search upgrade issues

Hi All,

Recently i upgraded elastic search version from 1.1.1 to 1.3.7 . Before 

upgrade when i create new index it will be replicate to other nodes
automatically but after upgrade elastic search to 1.3.7 version shards are
not allocating to replica node it is residing on primary node only. since
cluster is showing the status is yellow.

please help where is the problem occurring.is it a problem with elastic 

search upgrade?

Thanks
phani.

--
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/a30bdc7d-e8eb-4c34-be0c-4627e62944ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Did you upgrade both nodes? Do the nodes have enough disk space?
Is java and Elasticsearch the same version on each node? Have you checked
your logs?

On 5 January 2015 at 16:27, phani.nadiminti@goktree.com wrote:

Hi All,

Recently i upgraded elastic search version from 1.1.1 to 1.3.7 .

Before upgrade when i create new index it will be replicate to other nodes
automatically but after upgrade elastic search to 1.3.7 version shards are
not allocating to replica node it is residing on primary node only. since
cluster is showing the status is yellow.

please help where is the problem occurring.is it a problem with

elastic search upgrade?

Thanks
phani.

--
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/a30bdc7d-e8eb-4c34-be0c-4627e62944ca%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a30bdc7d-e8eb-4c34-be0c-4627e62944ca%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/CAEYi1X9mOg%2BhaBDKdMQTKYhOrcamUvr_no%3DxqRZ5SRV31PPpag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi Mark,

Thank you for the quick reply. i upgraded both nodes in elastic search.

the following are the diskspaces in each node

node 1 : 3Gb available out of 35 GB
node 2 : 4GB available out of 35 GB

  is this be a problem?

    yes java and elastic search has same versions on each nodes.

     java version using : "1.7.0_55"

On Monday, January 5, 2015 11:30:06 AM UTC+5:30, Mark Walkom wrote:

Did you upgrade both nodes? Do the nodes have enough disk space?
Is java and Elasticsearch the same version on each node? Have you checked
your logs?

On 5 January 2015 at 16:27, <phani.n...@goktree.com <javascript:>> wrote:

Hi All,

Recently i upgraded elastic search version from 1.1.1 to 1.3.7 . 

Before upgrade when i create new index it will be replicate to other nodes
automatically but after upgrade elastic search to 1.3.7 version shards are
not allocating to replica node it is residing on primary node only. since
cluster is showing the status is yellow.

please help where is the problem occurring.is it a problem with 

elastic search upgrade?

Thanks
phani.

--
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/a30bdc7d-e8eb-4c34-be0c-4627e62944ca%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a30bdc7d-e8eb-4c34-be0c-4627e62944ca%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/0c7a9159-db3c-42da-bcbb-6eca1421cd06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On Monday, January 05, 2015 at 10:13 CET, phani.nadiminti@goktree.com wrote:

Thank you for the quick reply. i upgraded both nodes in elastic
search.
the following are the diskspaces in each node
node 1 : 3Gb available out of 35 GB
node 2 : 4GB available out of 35 GB
is this be a problem?
yes java and elastic search has same versions on each nodes.
java version using : "1.7.0_55"

Yes, this is probably your problem. By default Elasticsearch won't
allocate shards on nodes with <15% free disk space.

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk

--
Magnus Bäck | Software Engineer, Development Tools
magnus.back@sonymobile.com | Sony Mobile Communications

--
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/20150105095715.GB12719%40seldlx20533.corpusers.net.
For more options, visit https://groups.google.com/d/optout.