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
This should never happen even if the bucket information got obsolete, instead keep handling operations by using obsolete ones on local and also try to keep the latency consistent (don't get into blocking due to waiting for RPC timeout).
The text was updated successfully, but these errors were encountered:
mocchira
changed the title
[leo_s3_libs] failed to fetch a bucket info after bucket_prop_sync_interval passed
[leo_s3_libs] failed to fetch a bucket info while both managers are down after bucket_prop_sync_interval passed
Mar 16, 2017
yosukehara
changed the title
[leo_s3_libs] failed to fetch a bucket info while both managers are down after bucket_prop_sync_interval passed
[leo_s3_libs] Failed to fetch a bucket info while both managers are down after bucket_prop_sync_interval passed
Apr 28, 2017
This cause the operations(GET|PUT|DELETE) to fail via S3 as reported on https://groups.google.com/forum/#!topic/leoproject_leofs/v_BAJT58Foo .
This should never happen even if the bucket information got obsolete, instead keep handling operations by using obsolete ones on local and also try to keep the latency consistent (don't get into blocking due to waiting for RPC timeout).
The text was updated successfully, but these errors were encountered: