问题描述
我已将以多主服务器模式设置的CosmosDB复制到多个站点，并且正在使用变更提要API从数据库中读取更新.目前，我正在从单个位置进行读取，但是不久以后，我计划从多个位置进行读取，以实现故障转移冗余.目前尚不清楚在这种情况下更改Feed API的行为方式.如果更改提要用来轮询更改的时间戳是直接从原始站点复制的，我可以想象到某些时序情况，其中更改提要将看不到更改，因为将来的Continuation Token已经存在.如果时间戳在复制的站点上更新，我不会有任何问题.虽然我可以自己进行测试以验证，但是我更希望知道CosmosDB团队明确支持的内容.
I have CosmosDB set up in multi-master mode replicated to several sites, and am utilizing the change feed API to read updates from the database. Currently I am reading from a single location, but soon I plan to read from multiple for failover redundancy. What isn't clear is how the change feed API is supposed to behave in this scenario. If the timestamp that change feed uses to poll for changes is copied directly from the originating site, I can imagine some timing situations where change feed would not see the changes since the Continuation Token is already in the future. I wouldn't expect any problems if the timestamp is updated on the replicated site. While I can test this myself to verify, I would prefer to know what is explicitly supported by the CosmosDB team.
推荐答案
所有区域中发生的所有更改都将复制到每个区域的更改提要中，因此您应该能够从任何区域中读取更改提要并获取所有毫无问题的变化.
All changes that happen in all regions are replicated to each region's Change Feed, so you should be able to read the Change Feed from any of the regions and obtain all the changes without issues.
这篇关于在多主复制的情况下，CosmosDB更改提要如何表现?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！