yes mark I am running same es version and java on both nodes.i have
iptables settings in my nodes is this be a problem? do we need to allow any
ports to resolve this issue I already allowed nodes communication ports
before..
Java version 1.7.0_75
Java(TM) SE Runtime Environment (build
You need to open 9300 between nodes to allow them to communicate, that's
likely the cause of this.
On 4 May 2015 at 16:06, phani.nadimi...@goktree.com wrote:
yes mark I am running same es version and java on both nodes.i have
iptables settings in my nodes is this be a problem? do we need to
I'd try disabling your firewall and eliminating it as a problem, checking
if the nodes can reach each other, and then going from there.
On 4 May 2015 at 20:23, phani.nadimi...@goktree.com wrote:
mark I opened that port already even though I am getting that warning...
[2015-05-04
Are you running the same ES and java versions on all your nodes and clients?
On 1 May 2015 at 21:21, phani.nadimi...@goktree.com wrote:
Hi All
i upgraded elastic search from 1.4.2 to 1.5.2 i am getting following
warning from console after upgrade please explain me the following error
Hi All
i upgraded elastic search from 1.4.2 to 1.5.2 i am getting following
warning from console after upgrade please explain me the following error
why it is coming.
[2015-05-01 06:15:13,361][WARN ][transport.netty ] [ES_Node1]
exception caught on transport layer [[id:
Any ideas?
On Wednesday, December 31, 2014 3:35:39 PM UTC+1, Georgeta wrote:
Hi All,
I have a 5 nodes cluster. I updated the cluster from 0.20.6 to 1.4.2.
When I start the cluster with shard allocation disabled, it starts and
goes into a yellow state, all good. When I enable shard
Thank you :)
On Tuesday, December 30, 2014 3:08:51 PM UTC+1, rcmuir wrote:
Yes. again, use the latest version (1.4.x). its very simple.
On Tue, Dec 30, 2014 at 8:53 AM, Georgeta Boanea gio...@gmail.com
javascript: wrote:
The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch
Hi All,
I have a 5 nodes cluster. I updated the cluster from 0.20.6 to 1.4.2.
When I start the cluster with shard allocation disabled, it starts and goes
into a yellow state, all good. When I enable shard allocation WARN messages
are generated:
INFO ||
Any ideas?
On Friday, December 19, 2014 11:40:37 AM UTC+1, Georgeta Boanea wrote:
Hi All,
After upgrading from ES 0.20.6 to 1.3.4 the following messages occurred:
[2014-12-19 10:02:06.714 GMT] WARN ||
elasticsearch[es-node-name][generic][T#14]
org.elasticsearch.cluster.action.shard
This bug occurs because you are upgrading to an old version of
elasticsearch (1.3.4). Try the latest version where the bug is fixed:
https://issues.apache.org/jira/browse/LUCENE-5975
On Fri, Dec 19, 2014 at 5:40 AM, Georgeta Boanea gio...@gmail.com wrote:
Hi All,
After upgrading from ES 0.20.6
The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
using Lucene 3.6, is it the same bug?
On Tuesday, December 30, 2014 2:08:48 PM UTC+1, Robert Muir wrote:
This bug occurs because you are upgrading to an old version of
elasticsearch (1.3.4). Try the latest version
Yes. again, use the latest version (1.4.x). its very simple.
On Tue, Dec 30, 2014 at 8:53 AM, Georgeta Boanea gio...@gmail.com wrote:
The Lucene bug is referring to 3.0-3.3 versions, Elasticsearch 0.20.6 is
using Lucene 3.6, is it the same bug?
On Tuesday, December 30, 2014 2:08:48 PM UTC+1,
Hi All,
After upgrading from ES 0.20.6 to 1.3.4 the following messages occurred:
[2014-12-19 10:02:06.714 GMT] WARN ||
elasticsearch[es-node-name][generic][T#14]
org.elasticsearch.cluster.action.shard [es-node-name] [index-name][3]
sending failed shard for [index-name][3],
Hi All,
I have elastic search version 1.1.1 i am planning to upgrade it to
1.3.4.let say i upgraded the ES node.how can we rollback es node to 1.1.1
again. or once we upgrade node ES can we roll back to 1.1.1 from 1.3.4
again is it possible?
Operating system using is Redhat enterprise
No you can’t downgrade.
You can restore your backups though if you snapshot before upgrading.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs
15 matches
Mail list logo
