KV rebalance stuck for Magma bucket on a Capella cluster

Issue
KV rebalance is stuck for more than 12 hours for default2 Magma bucket on a Capella AWS cluster after successful movement of 806 out of 896 vBuckets.

Steps

1. Deploy 3 node Capella AWS cluster with all services and running on 7.1.3 GA server version.
2. Create mixture of Couchstore and Magma buckets.
3. Import travel-sample bucket.
4. Create multiple scopes and collections for all buckets present in the cluster. default2 bucket for which the rebalance is stuck contains 4 scopes in addition to _default scope and 5 collections in each of these 4 scopes.
5. Load documents into 3 of the buckets including default2.
6. Trigger scale out operation by changing number of nodes from 3 to 5.

Observation
Cluster status is shown as scaling even after 12 hours.
Logged into 1 of the nodes and observed that rebalance is stuck for default2 bucket.
There has been no progress in data movement for more than 10 hours.