these two settings to not have a lot in common, wondering in what context
you see them the same.
minimum_master_nodes setting is only about the count of available nodes,
which are eligible to become a master in order to actually have an existing
master in a cluster.
write_consistency qourum is actually a check when a document is indexed
(and not about the nodes in a cluster) in order to decide if the document
should be written at all (before it is actually indexed)
How does minimum_master_nodes differ from action.write_consistency? Would
setting write_consistency to quorum help when minimum_master is not set
appropriately?
On Thu, Jan 16, 2014 at 6:08 AM, Norberto Meijome numard@gmail.comwrote:
So the checks are made in that order? 1) enough master nodes are available
2) Within that cluster decide how many replicas would acknowledge success
before returning back to the client
In other words just by having write_consistency set to quorum it doesn't
gurantee protection against split brain.
On Thu, Feb 6, 2014 at 1:30 AM, Alexander Reelsen alr@spinscale.de wrote:
Hey,
these two settings to not have a lot in common, wondering in what context
you see them the same.
minimum_master_nodes setting is only about the count of available nodes,
which are eligible to become a master in order to actually have an existing
master in a cluster.
write_consistency qourum is actually a check when a document is indexed
(and not about the nodes in a cluster) in order to decide if the document
should be written at all (before it is actually indexed)
How does minimum_master_nodes differ from action.write_consistency? Would
setting write_consistency to quorum help when minimum_master is not set
appropriately?
On Thu, Jan 16, 2014 at 6:08 AM, Norberto Meijome numard@gmail.comwrote:
not sure, if I made my point clear here:
The minimum_master_nodes is an important setting, if a master node election
is about to happen (this is not checked for each write of a document).
The write_consistency is a check, when a document is about to be stored.
Also note, that this check happens, before the data is written to the
primary shard. (This is not checked during a master election).
So the checks are made in that order? 1) enough master nodes are available
2) Within that cluster decide how many replicas would acknowledge success
before returning back to the client
In other words just by having write_consistency set to quorum it doesn't
gurantee protection against split brain.
On Thu, Feb 6, 2014 at 1:30 AM, Alexander Reelsen alr@spinscale.dewrote:
Hey,
these two settings to not have a lot in common, wondering in what context
you see them the same.
minimum_master_nodes setting is only about the count of available nodes,
which are eligible to become a master in order to actually have an existing
master in a cluster.
write_consistency qourum is actually a check when a document is indexed
(and not about the nodes in a cluster) in order to decide if the document
should be written at all (before it is actually indexed)
How does minimum_master_nodes differ from action.write_consistency?
Would setting write_consistency to quorum help when minimum_master is not
set appropriately?
On Thu, Jan 16, 2014 at 6:08 AM, Norberto Meijome numard@gmail.comwrote:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.