New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jewel: multisite: metadata master can get the wrong value for 'oldest_log_period' #11868
Conversation
RGWMetadataManager no longer makes stat calls on logs shards to determine its oldest_log_period. Instead, it records the oldest log's period id and realm_epoch in a rados object. If RGWMetadataManager::init_oldest_log_period() finds no such object, it calls find_oldest_period() to read period predecessors until it reaches the realm's first period, and writes that to rados. RGWMetadataManager::init_oldest_log_period() is now only called from RGWRados::init_complete() if run_sync_threads is true, instead of running unconditionally in RGWMetadataManager::init(), which allows us to skip building up a period history for radosgw-admin. Now that RGWMetadataManager::read_oldest_log_period() can return ENOENT for an uninitialized mdlog history, RGWRemoteMetaLog::run_sync() will retry on ENOENT as well. Fixes: http://tracker.ceph.com/issues/16894 Signed-off-by: Casey Bodley <cbodley@redhat.com> (cherry picked from commit d32654b) Conflicts: src/rgw/rgw_rados.cc: trivial context resolution
jenkins test this please (general jenkins failure) |
…the wrong value for 'oldest_log_period' Reviewed-by: Loic Dachary <ldachary@redhat.com>
@yehudasa does this backport look good to merge ? It passed the rgw suite http://tracker.ceph.com/issues/17851#note-3 . Note that it will not be in 10.2.4, reason why it targets jewel-next. |
…the wrong value for 'oldest_log_period' Reviewed-by: Loic Dachary <ldachary@redhat.com>
…the wrong value for 'oldest_log_period' Reviewed-by: Loic Dachary <ldachary@redhat.com>
@yehudasa ping |
check this please |
1 similar comment
check this please |
This passed more rgw runs at http://tracker.ceph.com/issues/17851#note-50 and http://tracker.ceph.com/issues/17851#note-58 |
|
http://tracker.ceph.com/issues/17512