[Feature]: Support more op messages to the mq

[SimFG]

Is there an existing issue for this?

• I have searched the existing issues

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

Support more op messages to the mq

Describe the solution you'd like.

No response

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

[SimFG]

/assign @SimFG
/unassign @xiaofan-luan

[jiaoew1991]

@SimFG Can you please elaborate on this issue in detail? This includes its use cases, impact on the current system, and how to ensure consistency between metadata and message queues.

[SimFG]

@jiaoew1991
For messages that do not currently exist in mq.

If they are collection categories, they will be hashed through collection_name to obtain a fixed channel, and such information will be forwarded to it, such as create index/drop index. For other types of messages, such as create database/drop database, a new channel will be created (set through yaml configuration), and all such information will be fixed to it.

This has no impact on the current system, and there is no additional meta information. The usage scenario is to use it for milvus incremental data synchronization, and further expand the master and backup disaster protection.

[SimFG]

/close

[sre-ci-robot]

@SimFG: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.