-
Notifications
You must be signed in to change notification settings - Fork 15
When the CDC stops the synchronization task, the data cannot be queried in the target environment. #194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
stops the synchronization task
targer milvus log |
Refresh the ATTU page. The following is the log output of the target environment. [2025/03/13 08:58:27.074 +00:00] [WARN] [delegator/delegator.go:482] ["delegator query failed to wait tsafe"] [traceID=dc423c5cd690d31f6c14f055a75e02d4] [collectionID=456616994539308425] [channel=by-dev-rootcoord-dml_0_456616994539308425v0] [replicaID=456616994701049857] [error="context deadline exceeded"] |
Restart the synchronization task. No data can be queried. [root@wy3-db241 milvus-cdc]# curl -X POST -H "Content-Type: application/json" -d '{
The CDC log output is as follows. [2025/03/13 17:00:57.147 +08:00] [INFO] [server/server.go:131] ["request receive"] [type=resume] [data="{"task_id":"847723f393fa4602893831c5001a006e"}"] |
@huangping11 Yes, you need to change ttMsgEnable of target milvus from false to true |
@SimFG Do I need to restart Milvus after the modification, and can it take effect online? |
Yes, but it will take a few seconds to take effect. |
@SimFG Do you mean that there is no need to restart after the modification, and it will automatically return to normal in a few minutes? |
@SimFG If it is a database that has been running for a period of time, can it be restored using a backup and then perform incremental synchronization? |
@SimFG I directly copied the volumes directory of the source database to the target environment. After starting the synchronization, I found that the data that had already been loaded and then deleted would not be synchronized to the target environment. |
yes, it can |
This will not work because the files will not be recognized by the new cluster, such as the collection id etc. |
@SimFG If the source environment is already in the running stage (with data), how can I use Milvus CDC to synchronize it to the target environment? Should we use milvus-backup to back up and restore to the target environment, and then perform incremental synchronization? |
@SimFG If it is possible to use the backup and restore method to build the Milvus-CDC synchronization, is the source environment allowed to write new data during the backup and restore process? If new data is written, will it lead to inconsistencies between the source environment and the target environment? |
@SimFG I found that changing the ttMsgEnable of the target Milvus from false to true won't take effect. It requires restarting the milvus-standalone to make it work. |
How do you determine that the ttMsgEnable configuration does not take effect? |
Do you have a need for active/standby disaster recovery? If so, you can communicate with our sales team. This capability cannot be achieved by CDC alone, and involves many details. At the same time, this part is also under development and testing, and there may be major changes in the future. Recently, our cloud will launch this function for beta testing. If it is for personal use, I recommend stopping the service and using CDC. If it is enterprise-level, you can wait until it is launched on the cloud and try it out. |
Current Behavior
[root@wy3-db241 milvus-cdc]# curl -X POST http://localhost:8444/cdc \
After the CDC (Change Data Capture) synchronization configuration is completed, newly inserted data has been successfully synchronized to the target environment, and queries can be performed in the target environment. However, once the synchronization task is stopped, the data cannot be queried.
source:
target:
It can be seen that the data in the target environment is consistent with that in the source environment.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: