From 4a42c72b5ede65f672fd41d775924fbd1be28840 Mon Sep 17 00:00:00 2001 From: Gyu-Ho Lee Date: Mon, 31 Oct 2016 07:59:33 -0700 Subject: [PATCH] op-guide: 'strict-reconfig-check' true by default --- Documentation/op-guide/runtime-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/op-guide/runtime-configuration.md b/Documentation/op-guide/runtime-configuration.md index c0fceb621..01054cbbf 100644 --- a/Documentation/op-guide/runtime-configuration.md +++ b/Documentation/op-guide/runtime-configuration.md @@ -169,7 +169,7 @@ As described in the above, the best practice of adding new members is to configu For avoiding this problem, etcd provides an option `-strict-reconfig-check`. If this option is passed to etcd, etcd rejects reconfiguration requests if the number of started members will be less than a quorum of the reconfigured cluster. -It is recommended to enable this option. However, it is disabled by default because of keeping compatibility. +It is enabled by default. [add member]: #add-a-new-member [cluster-reconf]: #cluster-reconfiguration-operations