neils-dev opened a new pull request #2518:
URL: https://github.com/apache/ozone/pull/2518


   ## What changes were proposed in this pull request?
   Problem: Intermittent failure with `testGetS3SecretAndRevokeS3Secret`.  
Occasionally, s3 secret is found after it has been revoked.
   On S3 Secret Revoke, specifically on call to `S3RevokeSecretRequest`, the s3 
secret is immediately stricken from the s3 secret cache however the action to 
remove from the s3 table is done through a transaction log batch job request.  
These transaction log batch requests are handled by a separate worker.  Due to 
this, there are times when the cache and s3 table are inconsistent, where the 
cache is consistent with the revoke request but the request has not yet 
propagated to the s3 table.  When a key is not found in the cache, it is looked 
up from the s3 table, hence the problem observed with intermittent integration 
test failure.
   
   This pr proposes a patch that within the `S3RevokeSecretRequest` 
repetitively checks the s3 table entry until it is removed or a timeout 
condition occurs.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-5358
   
   ## How was this patch tested?
   
   Patch tested through integration test on CI environment through git action 
workflow:
   https://github.com/neils-dev/ozone/actions/runs/1115101396
   
   `hadoop-ozone/dev-support/checks/integration.sh`
   with environment variables `$ITERATIONS=60, $MAVEN_OPTS: 
-Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false 
-Dmaven.wagon.http.retryHandler.class=standard 
-Dmaven.wagon.http.retryHandler.count=3`
   
   `hadoop-ozone/dev-support/checks/integration.sh 
-Dtest=TestSecureOzoneCluster#testGetS3SecretAndRevokeS3Secret`
   


-- 
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]

Reply via email to