[
https://issues.apache.org/jira/browse/HADOOP-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated HADOOP-11157:
---------------------------------
Attachment: HADOOP-11157.5.patch
Uploading test case fix..
The reason for your error : Since it is possible that there can be a delay for
the cancel token message initiated by one node to reach another node.. The
second node can ofcourse verify with ZK directly if the token that needs
verification has been cancelled or not before verification but.. that would
mean having to make an RPC call for every verification request.
Thus, the eventual consistency tradef-off should be acceptable here...
In this patch, I have
* Updated testcases to handle this (If failure is expected on verification, it
retires couple of times till it fails)
* All test cases run 10 times (please modify the TEST_RETRIES constant locally
for anything more.. I verified locally with 100 retries)
> ZKDelegationTokenSecretManager never shuts down listenerThreadPool
> ------------------------------------------------------------------
>
> Key: HADOOP-11157
> URL: https://issues.apache.org/jira/browse/HADOOP-11157
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.6.0
> Reporter: Gregory Chanan
> Assignee: Arun Suresh
> Attachments: HADOOP-11157.2.patch, HADOOP-11157.3.patch,
> HADOOP-11157.4.patch, HADOOP-11157.5.patch, HADOOP-11157.patch,
> HADOOP-11157.patch
>
>
> I'm trying to integrate Solr with the DelegationTokenAuthenticationFilter and
> running into this issue. The solr unit tests look for leaked threads and
> when I started using the ZKDelegationTokenSecretManager it started reporting
> leaks. Shuting down the listenerThreadPool after the objects that use it
> resolves the leak threads errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
