sun

> @lwclover I have read all the code. This solution is simple and useful in some cases. > > And the same time, there are two potential problems. > >...

> @lwclover This solution is enough for an inner network inside an organization. It may not be enough for common use cases. > > And this issue is so important...

> IMO, we can refer to affinity/anti-affinity in k8s. each broker can be labeled some tag, such as idc, rack and so on. namesrv hold broker's tag info through heartbeat....

> I think we need more discussions about this feature and implementation. I have two points: > > 1. Is there any chance to implement this feature through the client...

OK，I will do it

> LGTM， but would you like to rebase your codebase first? it seems this PR contained so many other's commits Next time. haha

The precise coder.