Does anyone have recommendations for setting `net_ticktime` to a lower value, such as 10, instead of the default 60? In particular, this would be for a 3-node cluster on bare metal connected to a single switch.
Background & why I’m asking: As far as I can tell, if a node fails in certain ways, the rest of the cluster can take up to 60 seconds (the default `net_ticktime`) to be aware of it—which can pause certain operations (such as a database creation) depending on the size of the cluster and quorum settings, etc. (For instance, in a 3-node cluster with a single failure, reads and writes continue to work, but creating a database waits until the _membership is up-to-date.) It looks like I can lower the Erlang `net_ticktime` setting to make this happen more quickly. The Erlang docs indicate that one should be cautious in changing this parameter, as it could lead to Couch thinking there were partitions when there were none—so I’m curious if anyone has any practical experience? Thanks! David Alan Hjelle 1 Corinthians 2:2 http://thehjellejar.com/ <http://thehjellejar.com/> <http://thehjellejar.com/>See the church management software I build at Icon Systems, Inc. <http://iconcmo.com/> Check out Rita’s spoons <http://jarofwood.com/>.
