From 8793c7342ad55c7ceece11f32bf73dc282a9ffc4 Mon Sep 17 00:00:00 2001 From: luomin Date: Sun, 18 Feb 2018 20:43:14 +0900 Subject: [PATCH] [FAB-8240] Document Orderer.Addresses config setting This changeset documents the `Orderer.Addresses` configuration parameter in `configtx.yaml` and readthedocs. Change-Id: Idbf35a2a3ba32f9db6ea6f33a1b214544c008ecd Signed-off-by: luomin Signed-off-by: Kostas Christids --- docs/source/ordering-service-faq.rst | 11 +++++++++++ sampleconfig/configtx.yaml | 6 +++++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/docs/source/ordering-service-faq.rst b/docs/source/ordering-service-faq.rst index 6335b79df84..c8a4e94731c 100644 --- a/docs/source/ordering-service-faq.rst +++ b/docs/source/ordering-service-faq.rst @@ -91,6 +91,17 @@ Solo Kafka ~~~~~ +:Question: + **How do I remove a node from the ordering service?** + +:Answer: + This is a two step-process: + + 1. Add the node's certificate to the relevant orderer's MSP CRL to prevent peers/clients from connecting to it. + 2. Prevent the node from connecting to the Kafka cluster by leveraging standard Kafka access control measures such as TLS CRLs, or firewalling. + +.. + :Question: **I have never deployed a Kafka/ZK cluster before, and I want to use the Kafka-based ordering service. How do I proceed?** diff --git a/sampleconfig/configtx.yaml b/sampleconfig/configtx.yaml index dac6c97f7bd..0b1f46be0f4 100644 --- a/sampleconfig/configtx.yaml +++ b/sampleconfig/configtx.yaml @@ -277,7 +277,11 @@ Orderer: &OrdererDefaults # Orderer Type: The orderer implementation to start. # Available types are "solo" and "kafka". OrdererType: solo - + + # Addresses here is a nonexhaustive list of orderers the peers and clients can + # connect to. Adding/removing nodes from this list has no impact on their + # participation in ordering. + # NOTE: In the solo case, this should be a one-item list. Addresses: - 127.0.0.1:7050