ArafatKhan2198 commented on PR #5445: URL: https://github.com/apache/ozone/pull/5445#issuecomment-1782616253
@ChenSammi The delay was due to the background Flush Thread not having committed the cache changes to the DB yet. This is expected, as there's a set time interval for flushing the data. Are you suggesting we skip the DB check for the revoked secret and only verify it after a flush is initiated? Additionally, the S3 secret could not get revoked because `S3SecretManager` thought that since the secret is not present in the cache hence we should check the table where it found it. but in reality the user had revoked it previously but `S3SecretManager` had no idea of knowing that since the entire entry was removed from the cache with no info about the previous revoked attempt. So, there's a mix-up, but it's more like confusion rather than an Inconsistency problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
