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
Topic recovery code uses retention settings as its cue for how much to restore to local disk. These should be changed to respect the local targets rather than the total retention.
Must also update tests to use these properties, and backport to 22.3.x
The text was updated successfully, but these errors were encountered:
Previously topic recovery would try and restore the entire
retention.[ms|bytes], which made sense when those properties
controlled local retention, but no longer makes sense since
22.3.x.
Fixes: redpanda-data#7490
Previously topic recovery would try and restore the entire
retention.[ms|bytes], which made sense when those properties
controlled local retention, but no longer makes sense since
22.3.x.
Fixes: redpanda-data#7490
jcsp
added a commit
to jcsp/redpanda
that referenced
this issue
Nov 24, 2022
Previously topic recovery would try and restore the entire
retention.[ms|bytes], which made sense when those properties
controlled local retention, but no longer makes sense since
22.3.x.
Fixes: redpanda-data#7490
Previously topic recovery would try and restore the entire
retention.[ms|bytes], which made sense when those properties
controlled local retention, but no longer makes sense since
22.3.x.
Fixes: redpanda-data#7490
(cherry picked from commit 43e9e19)
Topic recovery code uses retention settings as its cue for how much to restore to local disk. These should be changed to respect the local targets rather than the total retention.
Must also update tests to use these properties, and backport to 22.3.x
The text was updated successfully, but these errors were encountered: