Try this:
{
template : whateverindex-*,
mappings : {
events : {
_timestamp : { enabled : true },
}
}
}
From: elasticsearch@googlegroups.com [mailto:elasticsearch@googlegroups.com] On
Behalf Of Jef Statham
Sent: Friday, December 19, 2014 12:09 PM
To:
In our environment our cluster is inside EC2/VPC. We have an ELB in front of
the cluster. We use DNS to assign a CNAME to the ELB for easier internal use.
The cluster is currently at 15 nodes, 3 of which are “master only, no data” and
associate themselves with the ELB. The ELB balances requests
On Fri, Nov 21, 2014 at 1:56 AM, Christian Hedegaard
chedega...@red5studios.commailto:chedega...@red5studios.com wrote:
FYI, I have found a solution that works (at least for me).
I’ve got a small cluster for testing, only 4 v1.3.5 nodes. What I’ve done is
bring up 4X new v1.4.0 nodes as data-only
masters by accident.
The strategy as described above by Christian Hedegaard should work, it is still
to be considered a work-around:
- setting up all new 1.4 nodes as not master eligible (data only)
- joining them to a 1.3.x cluster while master still is on a 1.3 node should
work
- then, shutting
-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 to exactly
@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 the
1.4 node and the master
I found this thread while trying to research the same issue and it looks like
there is currently no resolution. We like to keep up on our elasticsearch
upgrades as often as possible and do rolling upgrades to keep our clusters up.
When testing I'm having the same issue, I cannot add a 1.4.0 box
