guhezhu01
guhezhu01
Another problem is that we are building a milvus cross cluster disaster recovery system, and using milvus backup and cdc to build a backup cluster. When testing the cdc incremental...
It will be solved later that after the backup synchronization, the data is written before the cdc starts. Is this part of data not synchronized
But this is a production environment. It is impossible to stop the normal use of the source cluster because of the establishment of a backup cluster
This scenario is mainly to establish a disaster recovery cluster. When the old cluster has problems, you can directly switch to the backup cluster. Or cluster migration
What component logs are required? After we set up the cdc synchronization, we started to synchronize normally, but then suddenly found that the target cluster could not be accessed, and...
We did not actively stop the cdc. Can you know why the cdc stopped? What does it mean that the target machine has no tt message?
In addition, I would like to ask you that restarting after stopping the cdc will not cause this problem
Not connected due to MySQL fluctuations? Can it be understood that this is the root cause? However, MySQL cannot be connected occasionally due to fluctuations, which is a normal situation....
We need to know the reason and whether the problem can be completely solved. It has not been widely used at present, otherwise there will always be similar problems in...
Thank you for your help. We need a conclusion. The current version of cdc is: v2.0.0-rc4