iilyak-ibm commented on PR #5603: URL: https://github.com/apache/couchdb/pull/5603#issuecomment-3180222883
> > What is your vision to handle a case when timestamps become inconsistent with each other on different nodes (for one reason or another)? > > There is some discussion about in first and second commit comments. There is the `_time_seq` endpoint to make the structure visible and it returns results from all shards, so users could detect if something is off. The structure can always be reset safely, without affecting the main data. The condition with it being out of sync is similar to a rewind which is expected sometimes and document it. In this case we also default to sending more data rather than less, that is if a shard copy is blown away and rebuilt, it's update will appear in the changes feed as it was created at the time when they replicated in. It's like a shard range get a rewind back to 0. So users should be prepared to reprocess the same rows like with regular sequences. If anyone needs to rely on strict timestamp it's up to them to insert explicit timestamp in the documents and index on them. Can we recreate _time_seq from the _time_seq of another node? We don't need to be exact, approximation of an age would do (correct up to the bin placement). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
