[ 
https://issues.apache.org/jira/browse/HADOOP-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870032#comment-16870032
 ] 

Hadoop QA commented on HADOOP-9930:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} 
| {color:red} HADOOP-9930 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-9930 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12601455/HADOOP-9930.2.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/16344/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Desync AbstractDelegationTokenSecretManager
> -------------------------------------------
>
>                 Key: HADOOP-9930
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9930
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.0.0-alpha, 3.0.0-alpha1
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Major
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-9930.2.patch, HADOOP-9930.patch
>
>
> The ADTSM is heavily synchronized.  The result is that verifying, creating, 
> renewing, and canceling tokens are all unnecessarily serialized.  The only 
> operations should be serialized are per-token renew and cancel operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to