Rebalance failed with reason "Partition 687 not in active nor passive set" in add in node rebalance

Rebalance failed with error

Rebalance exited with reason {{{{badmatch,
{error,
{error,
<<"Partition 36 not in active nor passive set">>}}},
[{capi_set_view_manager,handle_call,3},
{gen_server,handle_msg,5},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]},
{gen_server,call,
['capi_set_view_manager-saslbucket',
{wait_index_updated,36},
infinity]}},
{gen_server,call,
[{'janitor_agent-saslbucket','ns_1@10.6.2.44'},
{if_rebalance,<0.32719.854>,
{wait_index_updated,36}},
infinity]}}

with or without consistent view enable.

** In orange cluser with build 2.0.0-1781, consistent view is enable by default and rebalance failed when add 2 nodes to cluster.

** In Iryna cluster, consistent view is disable. She got rebalance failed with the same error as she mentioned in the following:

 index_aware_rebalance_disabled set false, 5 ddocs, 500K items
4 nodes cluster, remove 2 nodes and add 1 node, start rebalance

Rebalance exited with reason {{error,
                                  <<"Partition 687 not in active nor passive set">>},
                              {gen_server,call,
                                  [{'janitor_agent-bucket-0',
                                       'ns_1@10.3.121.120'},
                                   {if_rebalance,<0.14888.6>,
                                       {wait_index_updated,953}},
                                   infinity]}}