Changes identified in Storage performance testing for legal tag update
Type of change
- Enhancement with some code cleanup.
Does this introduce a change in the core logic?
Does this introduce a change in the cloud provider implementation, if so which cloud?
Does this introduce a breaking change?
What is the current behavior?
If the feature flag for legal tag update is enabled and storage service is on >1 pods, all api requests start giving 415 Unsupported Media Type error after a few successful requests. This is happening because thread context(request headers) is not getting cleared properly and new requests are using older values for Thread Local variables.
What is the new/expected behavior?
The context will be cleared for any new api requests where we need to set new headers explicitly, this will ensure that even when an old thread is picked from the thread pool for a new request, it's context is cleared before hand and we dont face 415 error code because of it.