You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ratis.apache.org by amaliujia <am...@apache.org> on 2026/09/01 02:38:41 UTC
[DISCUSS] Ratis 3.3.1 release
Hi Ratis developers,
I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
because we identified a few issues when upgrading downstream
applications to Ratis 3.3.0.
We fixed two noticeable issues:
1. RATIS-2680: Maintain backward compatibility for
SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
3.3.0).
2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
the follower snapshot covers the previous log entry. Without this fix,
a Ratis `TransferLeadership` API will never succeed under the certain
scenario.
Please let me know your thoughts.
Thanks,
Rui Wang
Re: [DISCUSS] Ratis 3.3.1 release
Posted by Haonan Hou <ha...@apache.org>.
Hi Tsz-Wo,
Thanks for the clarification. That sounds good to me. Let's target RATIS-2681
for the next 3.4.0 release.
Thanks,
Haonan
On 2026/09/03 17:34:48 Tsz Wo Sze wrote:
> Hi Haonan,
>
> > There are two small improvements from me: RATIS-2638 has been merged,
> while RATIS-2681 is still under review:
>
> If it is useful for you, we may include RATIS-2638 since the change is
> quite simple and the risk is low.
>
> For RATIS-2681, I have not reviewed it in detail but it does look like not
> a small change to GrpcLogAppender. So, let's not include it in a
> maintenance release.
>
> We may roll another 3.4.0 release as soon as it is ready. We can also
> consider including additional improvements later on, as rolling a new
> release in Ratis is relatively straightforward.
>
> Tsz-Wo
>
>
>
> On Thu, Sep 3, 2026 at 8:06 AM amaliujia <am...@apache.org> wrote:
>
> > Hi Haonan,
> >
> > I do want to release the maintenance release ASAP to address the
> > issues we identified in 3.3.0.
> >
> > Although we are targeting bug fixes, instead of cherry-picking and
> > stacking a few commits onto 3.3.0, I usually just cut the Release
> > Candidates from the head of the latest main branch.
> >
> > I have already cut the RC0, so whatever you have merged is included.
> > If RC0 fails, depending on the reason and whether your unmerged code
> > can be merged, your un-merged improvements might be included in the
> > other RCs.
> >
> > -Rui
> >
> > On Thu, Sep 3, 2026 at 5:38 PM Haonan Hou <ha...@apache.org> wrote:
> > >
> > > Hi Rui,
> > >
> > > Will 3.3.1 be limited to bug fixes, or can it also include small
> > improvements?
> > >
> > > There are two small improvements from me: RATIS-2638 has been merged,
> > while
> > > RATIS-2681 is still under review:
> > >
> > > https://issues.apache.org/jira/browse/RATIS-2638
> > > https://issues.apache.org/jira/browse/RATIS-2681
> > >
> > > Would they be suitable for 3.3.1?
> > >
> > > Thanks,
> > > Haonan
> > >
> > > On 2026/09/03 02:12:13 amaliujia wrote:
> > > > As there is no other objection, I will go forward to cut RC.
> > > >
> > > > I will make sure RATIS-2661 included into the RC.
> > > >
> > > > -Rui
> > > >
> > > > On Tue, Sep 1, 2026 at 4:18 PM Haonan Hou <ha...@apache.org> wrote:
> > > > >
> > > > > Hi Rui and Ratis developers,
> > > > >
> > > > > I'd like to propose including RATIS-2661 in the 3.3.1 maintenance
> > release:
> > > > >
> > > > > https://issues.apache.org/jira/browse/RATIS-2661
> > > > >
> > > > > This issue was discovered in IoTDB and may leave a recovered Raft
> > group
> > > > > permanently stuck in STARTING. The fix has already been merged into
> > master
> > > > > via PR #1564:
> > > > >
> > > > > https://github.com/apache/ratis/pull/1564
> > > > >
> > > > > Thanks,
> > > > > Haonan
> > > > >
> > > > > On 2026/09/01 04:26:55 amaliujia wrote:
> > > > > > Thank you! I can certainly help release this maintenance release.
> > > > > >
> > > > > > If there is no other objections, and if there are other bug fixes
> > that
> > > > > > people want to include into this maintenance release, please post
> > it
> > > > > > in this thread.
> > > > > >
> > > > > >
> > > > > > -Rui
> > > > > >
> > > > > > On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org>
> > wrote:
> > > > > > >
> > > > > > > +1
> > > > > > > Thanks for starting the release discussion!
> > > > > > >
> > > > > > > We may consider adding other bug fixes and improvements.
> > > > > > >
> > > > > > > BTW, 3.3.1 should be called a maintenance release
> > (major.minor.maintenance).
> > > > > > >
> > > > > > > Tsz-Wo
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org>
> > wrote:
> > > > > > >
> > > > > > > > Hi Ratis developers,
> > > > > > > >
> > > > > > > > I propose a release as Ratis 3.3.1 (a minor release following
> > 3.3.0)
> > > > > > > > because we identified a few issues when upgrading downstream
> > > > > > > > applications to Ratis 3.3.0.
> > > > > > > >
> > > > > > > > We fixed two noticeable issues:
> > > > > > > > 1. RATIS-2680: Maintain backward compatibility for
> > > > > > > > SimpleStateMachineStorage.cleanupOldSnapshots (related to
> > RATIS-224 in
> > > > > > > > 3.3.0).
> > > > > > > > 2. RATIS-2500: Fix the infinite InstallSnapshot notification
> > loop when
> > > > > > > > the follower snapshot covers the previous log entry. Without
> > this fix,
> > > > > > > > a Ratis `TransferLeadership` API will never succeed under the
> > certain
> > > > > > > > scenario.
> > > > > > > >
> > > > > > > >
> > > > > > > > Please let me know your thoughts.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Rui Wang
> > > > > > > >
> > > > > >
> > > >
> >
>
Re: [DISCUSS] Ratis 3.3.1 release
Posted by Tsz Wo Sze <sz...@apache.org>.
Hi Haonan,
> There are two small improvements from me: RATIS-2638 has been merged,
while RATIS-2681 is still under review:
If it is useful for you, we may include RATIS-2638 since the change is
quite simple and the risk is low.
For RATIS-2681, I have not reviewed it in detail but it does look like not
a small change to GrpcLogAppender. So, let's not include it in a
maintenance release.
We may roll another 3.4.0 release as soon as it is ready. We can also
consider including additional improvements later on, as rolling a new
release in Ratis is relatively straightforward.
Tsz-Wo
On Thu, Sep 3, 2026 at 8:06 AM amaliujia <am...@apache.org> wrote:
> Hi Haonan,
>
> I do want to release the maintenance release ASAP to address the
> issues we identified in 3.3.0.
>
> Although we are targeting bug fixes, instead of cherry-picking and
> stacking a few commits onto 3.3.0, I usually just cut the Release
> Candidates from the head of the latest main branch.
>
> I have already cut the RC0, so whatever you have merged is included.
> If RC0 fails, depending on the reason and whether your unmerged code
> can be merged, your un-merged improvements might be included in the
> other RCs.
>
> -Rui
>
> On Thu, Sep 3, 2026 at 5:38 PM Haonan Hou <ha...@apache.org> wrote:
> >
> > Hi Rui,
> >
> > Will 3.3.1 be limited to bug fixes, or can it also include small
> improvements?
> >
> > There are two small improvements from me: RATIS-2638 has been merged,
> while
> > RATIS-2681 is still under review:
> >
> > https://issues.apache.org/jira/browse/RATIS-2638
> > https://issues.apache.org/jira/browse/RATIS-2681
> >
> > Would they be suitable for 3.3.1?
> >
> > Thanks,
> > Haonan
> >
> > On 2026/09/03 02:12:13 amaliujia wrote:
> > > As there is no other objection, I will go forward to cut RC.
> > >
> > > I will make sure RATIS-2661 included into the RC.
> > >
> > > -Rui
> > >
> > > On Tue, Sep 1, 2026 at 4:18 PM Haonan Hou <ha...@apache.org> wrote:
> > > >
> > > > Hi Rui and Ratis developers,
> > > >
> > > > I'd like to propose including RATIS-2661 in the 3.3.1 maintenance
> release:
> > > >
> > > > https://issues.apache.org/jira/browse/RATIS-2661
> > > >
> > > > This issue was discovered in IoTDB and may leave a recovered Raft
> group
> > > > permanently stuck in STARTING. The fix has already been merged into
> master
> > > > via PR #1564:
> > > >
> > > > https://github.com/apache/ratis/pull/1564
> > > >
> > > > Thanks,
> > > > Haonan
> > > >
> > > > On 2026/09/01 04:26:55 amaliujia wrote:
> > > > > Thank you! I can certainly help release this maintenance release.
> > > > >
> > > > > If there is no other objections, and if there are other bug fixes
> that
> > > > > people want to include into this maintenance release, please post
> it
> > > > > in this thread.
> > > > >
> > > > >
> > > > > -Rui
> > > > >
> > > > > On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org>
> wrote:
> > > > > >
> > > > > > +1
> > > > > > Thanks for starting the release discussion!
> > > > > >
> > > > > > We may consider adding other bug fixes and improvements.
> > > > > >
> > > > > > BTW, 3.3.1 should be called a maintenance release
> (major.minor.maintenance).
> > > > > >
> > > > > > Tsz-Wo
> > > > > >
> > > > > >
> > > > > > On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org>
> wrote:
> > > > > >
> > > > > > > Hi Ratis developers,
> > > > > > >
> > > > > > > I propose a release as Ratis 3.3.1 (a minor release following
> 3.3.0)
> > > > > > > because we identified a few issues when upgrading downstream
> > > > > > > applications to Ratis 3.3.0.
> > > > > > >
> > > > > > > We fixed two noticeable issues:
> > > > > > > 1. RATIS-2680: Maintain backward compatibility for
> > > > > > > SimpleStateMachineStorage.cleanupOldSnapshots (related to
> RATIS-224 in
> > > > > > > 3.3.0).
> > > > > > > 2. RATIS-2500: Fix the infinite InstallSnapshot notification
> loop when
> > > > > > > the follower snapshot covers the previous log entry. Without
> this fix,
> > > > > > > a Ratis `TransferLeadership` API will never succeed under the
> certain
> > > > > > > scenario.
> > > > > > >
> > > > > > >
> > > > > > > Please let me know your thoughts.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Rui Wang
> > > > > > >
> > > > >
> > >
>
Re: [DISCUSS] Ratis 3.3.1 release
Posted by amaliujia <am...@apache.org>.
Hi Haonan,
I do want to release the maintenance release ASAP to address the
issues we identified in 3.3.0.
Although we are targeting bug fixes, instead of cherry-picking and
stacking a few commits onto 3.3.0, I usually just cut the Release
Candidates from the head of the latest main branch.
I have already cut the RC0, so whatever you have merged is included.
If RC0 fails, depending on the reason and whether your unmerged code
can be merged, your un-merged improvements might be included in the
other RCs.
-Rui
On Thu, Sep 3, 2026 at 5:38 PM Haonan Hou <ha...@apache.org> wrote:
>
> Hi Rui,
>
> Will 3.3.1 be limited to bug fixes, or can it also include small improvements?
>
> There are two small improvements from me: RATIS-2638 has been merged, while
> RATIS-2681 is still under review:
>
> https://issues.apache.org/jira/browse/RATIS-2638
> https://issues.apache.org/jira/browse/RATIS-2681
>
> Would they be suitable for 3.3.1?
>
> Thanks,
> Haonan
>
> On 2026/09/03 02:12:13 amaliujia wrote:
> > As there is no other objection, I will go forward to cut RC.
> >
> > I will make sure RATIS-2661 included into the RC.
> >
> > -Rui
> >
> > On Tue, Sep 1, 2026 at 4:18 PM Haonan Hou <ha...@apache.org> wrote:
> > >
> > > Hi Rui and Ratis developers,
> > >
> > > I'd like to propose including RATIS-2661 in the 3.3.1 maintenance release:
> > >
> > > https://issues.apache.org/jira/browse/RATIS-2661
> > >
> > > This issue was discovered in IoTDB and may leave a recovered Raft group
> > > permanently stuck in STARTING. The fix has already been merged into master
> > > via PR #1564:
> > >
> > > https://github.com/apache/ratis/pull/1564
> > >
> > > Thanks,
> > > Haonan
> > >
> > > On 2026/09/01 04:26:55 amaliujia wrote:
> > > > Thank you! I can certainly help release this maintenance release.
> > > >
> > > > If there is no other objections, and if there are other bug fixes that
> > > > people want to include into this maintenance release, please post it
> > > > in this thread.
> > > >
> > > >
> > > > -Rui
> > > >
> > > > On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org> wrote:
> > > > >
> > > > > +1
> > > > > Thanks for starting the release discussion!
> > > > >
> > > > > We may consider adding other bug fixes and improvements.
> > > > >
> > > > > BTW, 3.3.1 should be called a maintenance release (major.minor.maintenance).
> > > > >
> > > > > Tsz-Wo
> > > > >
> > > > >
> > > > > On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org> wrote:
> > > > >
> > > > > > Hi Ratis developers,
> > > > > >
> > > > > > I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
> > > > > > because we identified a few issues when upgrading downstream
> > > > > > applications to Ratis 3.3.0.
> > > > > >
> > > > > > We fixed two noticeable issues:
> > > > > > 1. RATIS-2680: Maintain backward compatibility for
> > > > > > SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
> > > > > > 3.3.0).
> > > > > > 2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
> > > > > > the follower snapshot covers the previous log entry. Without this fix,
> > > > > > a Ratis `TransferLeadership` API will never succeed under the certain
> > > > > > scenario.
> > > > > >
> > > > > >
> > > > > > Please let me know your thoughts.
> > > > > >
> > > > > > Thanks,
> > > > > > Rui Wang
> > > > > >
> > > >
> >
Re: [DISCUSS] Ratis 3.3.1 release
Posted by Haonan Hou <ha...@apache.org>.
Hi Rui,
Will 3.3.1 be limited to bug fixes, or can it also include small improvements?
There are two small improvements from me: RATIS-2638 has been merged, while
RATIS-2681 is still under review:
https://issues.apache.org/jira/browse/RATIS-2638
https://issues.apache.org/jira/browse/RATIS-2681
Would they be suitable for 3.3.1?
Thanks,
Haonan
On 2026/09/03 02:12:13 amaliujia wrote:
> As there is no other objection, I will go forward to cut RC.
>
> I will make sure RATIS-2661 included into the RC.
>
> -Rui
>
> On Tue, Sep 1, 2026 at 4:18 PM Haonan Hou <ha...@apache.org> wrote:
> >
> > Hi Rui and Ratis developers,
> >
> > I'd like to propose including RATIS-2661 in the 3.3.1 maintenance release:
> >
> > https://issues.apache.org/jira/browse/RATIS-2661
> >
> > This issue was discovered in IoTDB and may leave a recovered Raft group
> > permanently stuck in STARTING. The fix has already been merged into master
> > via PR #1564:
> >
> > https://github.com/apache/ratis/pull/1564
> >
> > Thanks,
> > Haonan
> >
> > On 2026/09/01 04:26:55 amaliujia wrote:
> > > Thank you! I can certainly help release this maintenance release.
> > >
> > > If there is no other objections, and if there are other bug fixes that
> > > people want to include into this maintenance release, please post it
> > > in this thread.
> > >
> > >
> > > -Rui
> > >
> > > On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org> wrote:
> > > >
> > > > +1
> > > > Thanks for starting the release discussion!
> > > >
> > > > We may consider adding other bug fixes and improvements.
> > > >
> > > > BTW, 3.3.1 should be called a maintenance release (major.minor.maintenance).
> > > >
> > > > Tsz-Wo
> > > >
> > > >
> > > > On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org> wrote:
> > > >
> > > > > Hi Ratis developers,
> > > > >
> > > > > I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
> > > > > because we identified a few issues when upgrading downstream
> > > > > applications to Ratis 3.3.0.
> > > > >
> > > > > We fixed two noticeable issues:
> > > > > 1. RATIS-2680: Maintain backward compatibility for
> > > > > SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
> > > > > 3.3.0).
> > > > > 2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
> > > > > the follower snapshot covers the previous log entry. Without this fix,
> > > > > a Ratis `TransferLeadership` API will never succeed under the certain
> > > > > scenario.
> > > > >
> > > > >
> > > > > Please let me know your thoughts.
> > > > >
> > > > > Thanks,
> > > > > Rui Wang
> > > > >
> > >
>
Re: [DISCUSS] Ratis 3.3.1 release
Posted by amaliujia <am...@apache.org>.
As there is no other objection, I will go forward to cut RC.
I will make sure RATIS-2661 included into the RC.
-Rui
On Tue, Sep 1, 2026 at 4:18 PM Haonan Hou <ha...@apache.org> wrote:
>
> Hi Rui and Ratis developers,
>
> I'd like to propose including RATIS-2661 in the 3.3.1 maintenance release:
>
> https://issues.apache.org/jira/browse/RATIS-2661
>
> This issue was discovered in IoTDB and may leave a recovered Raft group
> permanently stuck in STARTING. The fix has already been merged into master
> via PR #1564:
>
> https://github.com/apache/ratis/pull/1564
>
> Thanks,
> Haonan
>
> On 2026/09/01 04:26:55 amaliujia wrote:
> > Thank you! I can certainly help release this maintenance release.
> >
> > If there is no other objections, and if there are other bug fixes that
> > people want to include into this maintenance release, please post it
> > in this thread.
> >
> >
> > -Rui
> >
> > On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org> wrote:
> > >
> > > +1
> > > Thanks for starting the release discussion!
> > >
> > > We may consider adding other bug fixes and improvements.
> > >
> > > BTW, 3.3.1 should be called a maintenance release (major.minor.maintenance).
> > >
> > > Tsz-Wo
> > >
> > >
> > > On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org> wrote:
> > >
> > > > Hi Ratis developers,
> > > >
> > > > I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
> > > > because we identified a few issues when upgrading downstream
> > > > applications to Ratis 3.3.0.
> > > >
> > > > We fixed two noticeable issues:
> > > > 1. RATIS-2680: Maintain backward compatibility for
> > > > SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
> > > > 3.3.0).
> > > > 2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
> > > > the follower snapshot covers the previous log entry. Without this fix,
> > > > a Ratis `TransferLeadership` API will never succeed under the certain
> > > > scenario.
> > > >
> > > >
> > > > Please let me know your thoughts.
> > > >
> > > > Thanks,
> > > > Rui Wang
> > > >
> >
Re: [DISCUSS] Ratis 3.3.1 release
Posted by Haonan Hou <ha...@apache.org>.
Hi Rui and Ratis developers,
I'd like to propose including RATIS-2661 in the 3.3.1 maintenance release:
https://issues.apache.org/jira/browse/RATIS-2661
This issue was discovered in IoTDB and may leave a recovered Raft group
permanently stuck in STARTING. The fix has already been merged into master
via PR #1564:
https://github.com/apache/ratis/pull/1564
Thanks,
Haonan
On 2026/09/01 04:26:55 amaliujia wrote:
> Thank you! I can certainly help release this maintenance release.
>
> If there is no other objections, and if there are other bug fixes that
> people want to include into this maintenance release, please post it
> in this thread.
>
>
> -Rui
>
> On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org> wrote:
> >
> > +1
> > Thanks for starting the release discussion!
> >
> > We may consider adding other bug fixes and improvements.
> >
> > BTW, 3.3.1 should be called a maintenance release (major.minor.maintenance).
> >
> > Tsz-Wo
> >
> >
> > On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org> wrote:
> >
> > > Hi Ratis developers,
> > >
> > > I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
> > > because we identified a few issues when upgrading downstream
> > > applications to Ratis 3.3.0.
> > >
> > > We fixed two noticeable issues:
> > > 1. RATIS-2680: Maintain backward compatibility for
> > > SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
> > > 3.3.0).
> > > 2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
> > > the follower snapshot covers the previous log entry. Without this fix,
> > > a Ratis `TransferLeadership` API will never succeed under the certain
> > > scenario.
> > >
> > >
> > > Please let me know your thoughts.
> > >
> > > Thanks,
> > > Rui Wang
> > >
>
Re: [DISCUSS] Ratis 3.3.1 release
Posted by amaliujia <am...@apache.org>.
Thank you! I can certainly help release this maintenance release.
If there is no other objections, and if there are other bug fixes that
people want to include into this maintenance release, please post it
in this thread.
-Rui
On Tue, Sep 1, 2026 at 12:00 PM Tsz Wo Sze <sz...@apache.org> wrote:
>
> +1
> Thanks for starting the release discussion!
>
> We may consider adding other bug fixes and improvements.
>
> BTW, 3.3.1 should be called a maintenance release (major.minor.maintenance).
>
> Tsz-Wo
>
>
> On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org> wrote:
>
> > Hi Ratis developers,
> >
> > I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
> > because we identified a few issues when upgrading downstream
> > applications to Ratis 3.3.0.
> >
> > We fixed two noticeable issues:
> > 1. RATIS-2680: Maintain backward compatibility for
> > SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
> > 3.3.0).
> > 2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
> > the follower snapshot covers the previous log entry. Without this fix,
> > a Ratis `TransferLeadership` API will never succeed under the certain
> > scenario.
> >
> >
> > Please let me know your thoughts.
> >
> > Thanks,
> > Rui Wang
> >
Re: [DISCUSS] Ratis 3.3.1 release
Posted by Tsz Wo Sze <sz...@apache.org>.
+1
Thanks for starting the release discussion!
We may consider adding other bug fixes and improvements.
BTW, 3.3.1 should be called a maintenance release (major.minor.maintenance).
Tsz-Wo
On Mon, Aug 31, 2026 at 7:39 PM amaliujia <am...@apache.org> wrote:
> Hi Ratis developers,
>
> I propose a release as Ratis 3.3.1 (a minor release following 3.3.0)
> because we identified a few issues when upgrading downstream
> applications to Ratis 3.3.0.
>
> We fixed two noticeable issues:
> 1. RATIS-2680: Maintain backward compatibility for
> SimpleStateMachineStorage.cleanupOldSnapshots (related to RATIS-224 in
> 3.3.0).
> 2. RATIS-2500: Fix the infinite InstallSnapshot notification loop when
> the follower snapshot covers the previous log entry. Without this fix,
> a Ratis `TransferLeadership` API will never succeed under the certain
> scenario.
>
>
> Please let me know your thoughts.
>
> Thanks,
> Rui Wang
>