Major Description
In a busy system, bucket topology service can end up using a lot of heap space and cause extra workload for garbage collector. This was evident from the findings in MB-48860.
Even if XDCR were to upgrade to golang 1.16 or later (MB-48888), the bucket topology service would still be pumping out garbage (allocate memoyr, use once, then toss).
We should revisit this service to make sure that it's more "environmental friendly" and not generating garbage as to be nice to other services.
