[Enhancement] Ensuring consistency between broker and nameserver data when deleting a topic

[RongtongJin]

Before Creating the Enhancement Request

• I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

I hope that by deleting the topic on the broker, it can be guaranteed that the corresponding routing on the NameServer will eventually be deleted, thus ensuring consistency between the data on both.

Motivation

Currently, the deletion of a topic involves two steps: deleting the topic on the broker and deleting it on all the NameServers. However, since this step is not atomic, if the program execution is interrupted after the broker topic is deleted, the routing on the NameServer will not be removed, leading to potential problems. To ensure data consistency, it is suggested that deleting the topic on the broker should guarantee the corresponding routing on the NameServer to be eventually removed.

Describe the Solution You'd Like

During the registration process, Nameserver compares the registered Topic with the existing Topic in the routing table, and removes invalid routes.

When performing incremental registration (such as creating a Topic), REGISTER_TOPIC_IN_NAMESRV requests are now used instead of REGISTER_BROKER requests.

Describe Alternatives You've Considered

No

Additional Context

No response