Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FAB-15648] hints to document: Non-TLS orderer with etcdraft usage (bp #1678) #2303

Merged
merged 1 commit into from
Jan 22, 2021
Merged

[FAB-15648] hints to document: Non-TLS orderer with etcdraft usage (bp #1678) #2303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions docs/source/raft_configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,22 +82,26 @@ other, and TLS certificates issued by a public TLS CA for the client facing API.

* `ClientCertificate`, `ClientPrivateKey`: The file path of the client TLS certificate
and corresponding private key.
* `ListenPort`: The port the cluster listens on. If blank, the port is the same
port as the orderer general port (`general.listenPort`)
* `ListenPort`: The port the cluster listens on.
It must be same as `consenters[i].Port` in Channel configuration.
If blank, the port is the same port as the orderer general port (`general.listenPort`)
* `ListenAddress`: The address the cluster service is listening on.
* `ServerCertificate`, `ServerPrivateKey`: The TLS server certificate key pair
which is used when the cluster service is running on a separate gRPC server
(different port).
* `SendBufferSize`: Regulates the number of messages in the egress buffer.

Note: `ListenPort`, `ListenAddress`, `ServerCertificate`, `ServerPrivateKey` must
be either set together or unset together.
If they are unset, they are inherited from the general TLS section,
in example `general.tls.{privateKey, certificate}`.
When general TLS is disabled:
- Use a different `ListenPort` than the orderer general port
- Properly configure TLS root CAs in the channel configuration.

There are also hidden configuration parameters for `general.cluster` which can be
used to further fine tune the cluster communication or replication mechanisms:

* `SendBufferSize`: Regulates the number of messages in the egress buffer.
* `DialTimeout`, `RPCTimeout`: Specify the timeouts of creating connections and
establishing streams.
* `ReplicationBufferSize`: the maximum number of bytes that can be allocated
Expand Down