huangping11

stops the synchronization task [root@wy3-db241 milvus-cdc]# curl -X POST -H "Content-Type: application/json" -d '{ > "request_type":"pause", > "request_data": { > "task_id": "847723f393fa4602893831c5001a006e" > } > }' http://localhost:8444/cdc {"code":200} [root@wy3-db241 milvus-cdc]#...

Refresh the ATTU page. No data can be queried.  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...

Restart the synchronization task. No data can be queried. [root@wy3-db241 milvus-cdc]# curl -X POST -H "Content-Type: application/json" -d '{ > "request_type":"resume", > "request_data": { > "task_id": "847723f393fa4602893831c5001a006e" > } >...

@SimFG Do I need to restart Milvus after the modification, and can it take effect online?

@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...

@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...

@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...

@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.