Skip to content

Commit

Permalink
[FAB-8647]: explain limitation of adding new org
Browse files Browse the repository at this point in the history
While adding new organization to the existed Fabric network there is a
limitation which requires to either setup all newly added peer to be
configured as a leaders or leverage dynamic leader election mechanism.
This commit add section to the channel update doc explaining the limitations.

Change-Id: I7ef1cb6804570f4d6764ca490de0a93bcfd979d4
Signed-off-by: Artem Barger <bartem@il.ibm.com>
  • Loading branch information
C0rWin committed Mar 5, 2018
1 parent 0103f32 commit 7a5a16e
Showing 1 changed file with 35 additions and 0 deletions.
35 changes: 35 additions & 0 deletions docs/source/channel_update_tutorial.rst
Original file line number Diff line number Diff line change
Expand Up @@ -487,6 +487,41 @@ Inspect the logs for ``peer0.org1.example.com``:
Follow the demonstrated process to fetch and decode the new config block if you wish to inspect
its contents.

Configuring Leader Election
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Newly joining peers are bootstrapped with the genesis block, which does not contain information about the organization
that is being added in the channel configuration update. Therefore new peers are not able to utilize gossip as
they cannot verify blocks forwarded by other peers from their own organization until they get the configuration
transaction which added the organization to the channel. Newly added peers must therefore have one of the following
configurations so that they receive blocks from the ordering service:

1. Utilize static leader mode and configure the peer to be an organization leader:

::

export CORE_PEER_GOSSIP_USELEADERELECTION=false
export CORE_PEER_GOSSIP_ORGLEADER=true


.. note:: This configuration must be the same for all new peers added to the channel.

2. Utilize dynamic leader election:

::

export CORE_PEER_GOSSIP_USELEADERELECTION=true
export CORE_PEER_GOSSIP_ORGLEADER=false


.. note:: Because peers of newly added organization won't be able to form membership view, this option will
be similar to the static configuration, as each peer will start proclaiming himself to be a leader.
However eventually once they get updated with the configuration transaction that adds the
organization to the channel, there will be only one active leader for the organization. Therefore it
is recommended to leverage this option if you eventually want the organization's peers to utilize
leader election.


Join Org3 to the Channel
~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down

0 comments on commit 7a5a16e

Please sign in to comment.