Firstly thanks to everyone who built and helps with elasticsearch, it is an
amazing piece of technology!
I have a question regarding cluster restarts:
I have been working on some river plugins on a cluster with the following
- 4 nodes
- 5 indexes with 10 shards each
- replication set to 2
The river plugins are the only thing modifying data on the cluster, so when
they aren't running, the data is static.
Here is the process I'm following when I need to redeploy a new version of
the river plugin:
For each node:
- Delete the _river index from the cluster, in order to stop any currently
- install the new version of the river plugin
- bounce the node and wait for cluster state to go green
- repeat for each node.
However, waiting for the cluster to go green in each of these steps takes
about 30 minutes per node, so the whole process is quite slow.
I am wondering about a couple of options that might speed this up:
Option 1 - close the indexes before bouncing the nodes, then open them once
all nodes are bounced (as nothing will be modifying the data during the
redeploy, I figure this might make the restarts a lot faster).
Option 2 - bounce 2 nodes at a time - as replication is set to 2, I figure
we can safely have 2 nodes down and still recover fully.
BTW - I'm assuming that I need to wait for the cluster state to be green
before continuing to bounce the other cluster nodes, but if this is not
correct, maybe I can save some time in that step as well.
Any suggestions on this would be appreciated.
On Tuesday, September 13, 2011 6:30:09 AM UTC+10, ppearcy wrote:
When I've restarted my cluster, I've observed that I very quickly (a
couple of minutes) get into the yellow state, while it takes much
longer (a couple of hours) to get into the green state.
I am using the local gateway and know that each node will pull it's
local data in order to get into the yellow state.
After that, do nodes use their own data to fulfill all replicas and
verify it against the master w/ checksums or is all the data synced
over from the master shard and the local data is disregarded?
Based on the performance I have observed, I believe it is the latter,
but wanted to confirm.
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.