[Remote Store] Change of behaviour in replica recovery for remote translog enabled indices #4527
Labels
distributed framework
enhancement
Enhancement or improvement to existing feature or request
Storage:Durability
Issues and PRs related to the durability framework
v2.5.0
'Issues and PRs related to version v2.5.0'
Is your feature request related to a problem? Please describe.
During the current replica recovery process, the high level flow goes like this -
and then
With the existing recovery mechanism, we rely on both the segments and the translog for deciding the sequence number upto which the replica already has got the data. This is also the seq no that is sent across transport service to the primary for starting the recovery process.
Now, with remote translog, the translog will not be stored on replicas any more for durability and that also necessitates the need for changing the recovery process to not account for translog anymore on replicas.
Describe the solution you'd like
Since underlying replication is segment replication, the segment files would be present and that would be used to start the recovery process from the max seq no in the last committed segment infos.
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: