You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We need to identify all such interaction points with checkpoints and mutates it while in primary shard. Currently checkpoints are used in a lot of areas directly or indirectly like Index commits, translogs, segments, insync shards, etc. But primarily it keeps track of how far are the replicas behind the primary. It also helps in deciding from what sequence number should the recovery happen on replicas since a definition of global / local checkpoint guarantees durability of data upto the sequence number it refers to.
Describe the solution you'd like
With no-op replication, the calls would not be reaching to the engine of the replica anymore. The calls would return to the primary before that itself. That kinds of makes the need of relying on the checkpoints unnecessary for primary and as well as replica. In this issue, we plan to remove the reliance only for primary shards
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We need to identify all such interaction points with checkpoints and mutates it while in primary shard. Currently checkpoints are used in a lot of areas directly or indirectly like Index commits, translogs, segments, insync shards, etc. But primarily it keeps track of how far are the replicas behind the primary. It also helps in deciding from what sequence number should the recovery happen on replicas since a definition of global / local checkpoint guarantees durability of data upto the sequence number it refers to.
Describe the solution you'd like
With no-op replication, the calls would not be reaching to the engine of the replica anymore. The calls would return to the primary before that itself. That kinds of makes the need of relying on the checkpoints unnecessary for primary and as well as replica. In this issue, we plan to remove the reliance only for primary shards
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: