From 50aea5e3468b6675ff3c09c4298c1680774ecfe1 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Fri, 14 Aug 2020 20:54:27 +0300 Subject: [PATCH] Update doc to reflect change in FAB-18163 (#1729) Signed-off-by: Jason Yellick (cherry picked from commit 9881a25f43bdf39436bd0eff1449d65a495dac29) Co-authored-by: Jason Yellick --- docs/source/raft_configuration.md | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/docs/source/raft_configuration.md b/docs/source/raft_configuration.md index 38c7db8a45a..3ec2a5f525b 100644 --- a/docs/source/raft_configuration.md +++ b/docs/source/raft_configuration.md @@ -122,16 +122,9 @@ used to further fine tune the cluster communication or replication mechanisms: To recover from such a scenario, it is possible to make TLS handshakes between ordering nodes consider the time to be shifted backwards a given amount that is configured to `TLSHandshakeTimeShift`. - In order to be as uninvasive as possible, this configuration option - only effects ordering nodes that use a separate gRPC server for their - intra-cluster communication. - If your cluster is communicating via the same gRPC server that is used - to service clients and peers, you need to first reconfigure your orderer - by additionally setting `general.cluster.ListenPort`, `general.cluster.ListenAddress`, - `ServerCertificate` and `ServerPrivateKey`, and then restarting the orderer - in order for the new configuration to take effect. - - + This setting only applies when a separate cluster listener is in use. If + the cluster service is sharing the orderer's main gRPC server, then instead + specify `TLSHandshakeTimeShift` in the `General.TLS` section. **Consensus parameters:**