Re: Indices not recovering after elasticsearch upgrade (1.0.2 -> 1.4.1)

Anyone? On Mon, Dec 1, 2014 at 11:22 AM, Michel Conrad wrote: > Hi, > > I just updated our test environment from 1.0.2 to 1.4.1 and some > indices failed to recover, which seems to be related to the checksum > verfication introduces in 1.3. > > [2014-11-

Indices not recovering after elasticsearch upgrade (1.0.2 -> 1.4.1)

Hi, I just updated our test environment from 1.0.2 to 1.4.1 and some indices failed to recover, which seems to be related to the checksum verfication introduces in 1.3. [2014-11-28 09:40:48,019][WARN ][cluster.action.shard ] [NODE1] [index][0] received shard failed for [index][0], node[CWq_u

Re: Disk-based shard allocation per node settings

vel setting. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 16 May 2014 17:43, Michel Conrad wrote: >> >> Is it possible to specify different thresholds fo

Disk-based shard allocation per node settings

Is it possible to specify different thresholds for different nodes in the cluster? I could not find it in the documentation, when updating the setting through the cluster settings as described on http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#dis

Re: Slow cluster startup with zen discovery and large number of nodes.

Also the kernel complains about too many connections being made at once on the joining node. (Seems to occur after 30 nodes joined the cluster) TCP: TCP: Possible SYN flooding on port 9300. Sending cookies. Check SNMP counters. On Fri, Feb 21, 2014 at 6:44 PM, Thibaut Britz wrote: > Hi, > > I'm

Slow cluster startup with zen discovery and large number of nodes.

Hi, Starting a cluster with 100 nodes takes half an hour just for the nodes to join in elasticsearch version 1.0. In version 0.19.8 nodes were very quick to join the cluster. The issue seems to come from the master node sending the updated state to all the nodes in the cluster after every single a

Re: Temporary disable river allocation (dynamic cluster setting?)

Hi, maybe its clearer with an example. Imagine I have 5 data node, 5 river nodes and 10 rivers running on these 5 river nodes. The data nodes are called N1 to N5, these have river set to false. The river nodes are called R1 to R5, these have river set to true. After creating the rivers or after a

Temporary disable river allocation (dynamic cluster setting?)

Is it possible to temporary disable river allocation? We want to separate the nodes running the rivers from the nodes holding the data, so that the nodes running the rivers can be temporary shut down or restarted without having an impact on the data nodes. After restarting the river nodes, all our