-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HADOOP-18316: ABFS: Add support for cache handling when filesystem instance has clientCorrelationID enabled #4512
base: trunk
Are you sure you want to change the base?
Conversation
:::: AGGREGATED TEST RESULT :::: HNS-OAuth[INFO] Results: HNS-SharedKey[INFO] Results: NonHNS-SharedKey[INFO] Results: AppendBlob-HNS-OAuth[INFO] Results: Time taken: 75 mins 22 secs. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
This is to mainly handle the scenarios for cache enablement or disablement when the filesystem instance has clientCorrelationId as a part of its configuration.
If a filesystem instance has clientCorrelationId as a part of its configuration and if we enable cache for the same, there may be another job using a filesystem instance with same configuration and uri as the one cached, but the issue here is that since these 2 filesystem instances are part of 2 different running jobs, they can't share the same clientCorrelationId.
So as a part of the fix, if a filesystem instance has clientCorrelationId we disable cache for that process, so that if any other job is running as a part of the same process with the same configuration and uri, the filesystem instance created as a part of it will be created as a new instance and hence will not report incorrect clientCorrelationId.
Our main aim here is to prevent incorrect clientCorrelationId from being reported.