ard to upgrading our current production cluster this way
(15 data-only nodes, 3 master-only nodes).
So it would appear that the problem is somewhere in the unicast discovery code.
The question is who’s to blame? Elasticsearch or the cloud-aws plugin?
From: Boaz Leskes [mailto:b.les...@gmail.com<
@googlegroups.com
Subject: Re: 1.4.0 data node can't join existing 1.3.4 cluster
Hi Christian, Daniel,
I believe I found the issue - it has to do with the cloud plugins (both AWS and
GCE) and the way they create the node list for the unicast based discovery.
Effectively they mislead it to think
v1.3.5 nodes to migrate the data off of
>>>> them. Before the final 1.3.5 node is nuked, I will change the config on
>>>> one
>>>> of the v1.4.0 nodes to allow it as master and restart it.
>>>>
>>>>
>>>>
>>>> I’m not sure if the master
er that I will
>>> be able to try this upgrade again with in a more controlled manner.
>>>
>>>
>>>
>>> I’m NOT looking forward to upgrading our current production cluster this
>>> way (15 data-only nodes, 3 master-only nodes).
>>>
&g
>> I’m NOT looking forward to upgrading our current production cluster this
>> way (15 data-only nodes, 3 master-only nodes).
>>
>>
>>
>> So it would appear that the problem is somewhere in the unicast discovery
>> code. The question is who’s to blame? Elast
Hi All,
I believe I found the source of the problem and it has to do with the AWS
plugin. I opened an issue for it, which should be pretty easy to
fix: https://github.com/elasticsearch/elasticsearch-cloud-aws/issues/143 .
Cheers,
Boaz
On Friday, November 21, 2014 5:39:32 PM UTC+2, Ivan Brusic
;
>
>
> *From:* Boaz Leskes [mailto:b.les...@gmail.com]
> *Sent:* Wednesday, November 19, 2014 2:27 PM
> *To:* elasticsearch@googlegroups.com
> *Cc:* Christian Hedegaard
> *Subject:* Re: 1.4.0 data node can't join existing 1.3.4 cluster
>
>
>
> Hi Christian,
Has an official issue been created? I would like to track the status.
So far, every 1.x.0 release has been buggy. :)
--
Ivan
On Fri, Nov 21, 2014 at 4:06 AM, Mark Walkom wrote:
> It's being looked at, but I don't know much beyond that at the moment
> sorry.
>
> On 21 November 2014 20:02, wro
Cool :)
Usually this means a fix will emerge. Thanks!
On Friday, November 21, 2014 10:07:03 AM UTC+1, Mark Walkom wrote:
>
> It's being looked at, but I don't know much beyond that at the moment
> sorry.
>
> On 21 November 2014 20:02, > wrote:
>
>> Is there any of the elasticsearch team members
It's being looked at, but I don't know much beyond that at the moment sorry.
On 21 November 2014 20:02, wrote:
> Is there any of the elasticsearch team members that can hint to whether or
> not this is something that will be fixed in 1.4.1? Then we'll simply wait
> for it instead of doing differ
Is there any of the elasticsearch team members that can hint to whether or
not this is something that will be fixed in 1.4.1? Then we'll simply wait
for it instead of doing different hacks to upgrade.
On Monday, November 17, 2014 12:35:03 PM UTC+1, Matthew Barrington wrote:
>
> I stand corrected
the cloud-aws plugin?
From: Boaz Leskes [mailto:b.les...@gmail.com]
Sent: Wednesday, November 19, 2014 2:27 PM
To: elasticsearch@googlegroups.com
Cc: Christian Hedegaard
Subject: Re: 1.4.0 data node can't join existing 1.3.4 cluster
Hi Christian,
I'm not sure what thread you refer
Leskes [mailto:b.le...@gmail.com ]
> *Sent:* Wednesday, November 19, 2014 2:27 PM
> *To:* elasti...@googlegroups.com
> *Cc:* Christian Hedegaard
> *Subject:* Re: 1.4.0 data node can't join existing 1.3.4 cluster
>
>
>
> Hi Christian,
>
>
>
> I
search@googlegroups.com
Cc: Christian Hedegaard
Subject: Re: 1.4.0 data node can't join existing 1.3.4 cluster
Hi Christian,
I'm not sure what thread you refer to exactly, but this shouldn't happen. Can
you describe the problem you have some more? Anything in the nodes? (both
Hi Christian,
I'm not sure what thread you refer to exactly, but this shouldn't happen.
Can you describe the problem you have some more? Anything in the nodes?
(both the 1.4 node and the master)
Cheers,
Boaz
On Wednesday, November 19, 2014 2:39:57 AM UTC+1, Christian Hedegaard wrote:
>
> I f
I stand corrected, this did not work on our main cluster.
On Monday, 17 November 2014 11:13:22 UTC, Matthew Barrington wrote:
>
> We are running a 1.3.4 cluster using the AWS plugin and I noticed the same
> error when I tried to upgrade a single node.
>
> Since I was trying this on my test cluste
We are running a 1.3.4 cluster using the AWS plugin and I noticed the same
error when I tried to upgrade a single node.
Since I was trying this on my test cluster first I decided to see what
would happen if I upgraded a 2nd node. Would it split into 2 clusters, have
the same issue, etc.
What I
On Fri, Nov 14, 2014 at 3:41 AM, wrote:
> I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 cluster
> with cloud-aws plugin version 2.4.0. Is there a workaround to use during
> upgrade, since I assume it's not a problem when they're all upgraded to
> 1.4.0.
I ended up starting
1.4.0 trying to join a 1.3.5 cluster with cloud-aws also fails.
On Friday, November 14, 2014 12:41:08 PM UTC+1, madsm...@colourbox.com
wrote:
>
> I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4
> cluster with cloud-aws plugin version 2.4.0. Is there a workaround to use
> dur
I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 cluster
with cloud-aws plugin version 2.4.0. Is there a workaround to use during
upgrade, since I assume it's not a problem when they're all upgraded to
1.4.0.
On Friday, November 14, 2014 11:33:45 AM UTC+1, Jörg Prante wrote:
I think this is only related to unicast. But, nevertheless, it *should*
work... not sure if this is a bug or a feature
Jörg
On Fri, Nov 14, 2014 at 12:58 AM, Eric Jain wrote:
> On Thu, Nov 13, 2014 at 10:05 AM, joergpra...@gmail.com
> wrote:
> > Do not mix 1.3 with 1.4 nodes, it does not w
On Thu, Nov 13, 2014 at 10:05 AM, joergpra...@gmail.com
wrote:
> Do not mix 1.3 with 1.4 nodes, it does not work.
If that is so, that seems like something the release notes should mention?
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To un
I discovered a peculiarity, well documented in the source
https://github.com/elasticsearch/elasticsearch/commit/e5de47d928582694c7729d199390086983779e6e
/**
* when pinging the initial configured target hosts, we do not know
their version. We therefore use
* the lowest possible versi
Rolling upgrades should be supported:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html#rolling-upgrades
How else can you perform a rolling upgrade without having a mixed cluster?
--
Ivan
On Thu, Nov 13, 2014 at 1:05 PM, joergpra...@gmail.com <
joergpra..
Do not mix 1.3 with 1.4 nodes, it does not work.
Jörg
On Thu, Nov 13, 2014 at 5:16 PM, Todd Kamin wrote:
> I'm seeing something very similar, also from 1.3.4 to 1.4.0, also using
> the elasticsearch-cloud-aws plugin 2.4.
>
> [2014-11-13 16:02:26,055][WARN ][discovery.zen.ping.unicast] [White Fa
I'm seeing something very similar, also from 1.3.4 to 1.4.0, also using the
elasticsearch-cloud-aws plugin 2.4.
[2014-11-13 16:02:26,055][WARN ][discovery.zen.ping.unicast] [White Fang]
failed to send ping to
[[#cloud-i-03f79bcb-0][localhost][inet[/10.0.0.76:9300]]]
org.elasticsearch.transport.
26 matches
Mail list logo
