feat(meta): better handle two compactor register with the same name.

[KeXiangWang]

Is your feature request related to a problem? Please describe.

One user use a service discovery to expose the container to each others. So when filling the argument advertise-addr of compactor, he uses a service discovery address. But When a component communicate with Meta through MetaClient, MetaClient identifies the component based on its advertise-addr . As a result, both of two compactors use the same advertise-addr . When a new compactor joins, Meta wrongly sends an Info::Snapshot notification to the running compactor, causing the running compactor panic.

Describe the solution you'd like

Better handle this situation.

1. Double check with other component.
2. If this happen, report some error instead of panic.
3. Add more documents to guide user to fill advertise-addr.

Describe alternatives you've considered

No response

Additional context

To reproduce:

Run docker compose up -d on https://github.com/risingwavelabs/risingwave/tree/wkx/print-notification.

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄