We are using version 17.6.
The reason to restart the cluster was an update of a plugin.
Here's the scenario:
- shut down the cluster
- start the none data node (node.data = false, no other node settings)
At this time this node was marked as master Node in BigDesk
- start the data nodes
-> data gone
Unfortunately I can not reproduce this scenario
On Tue, Aug 23, 2011 at 8:57 PM, Shay Banon firstname.lastname@example.org wrote:
This configuration should is valid and should not result in loss of data. I
wonder if you hit something I fixed in master/0.17 branch:
Can you provide the steps that led to loosing the data? I would like to
recreate it. For example: Start the non_data/master node, then start a
data/non_master node, index some sample data, shut it down, start it in the
same order, ... .
On Tue, Aug 23, 2011 at 6:07 PM, Jürgen kartnaller <
If you have node.data set to false it is important to set node.master to
If a none data node becomes a master the whole cluster data gets lost on a
It would be a good idea to automatically set node.master to false if
node.data is set to true.