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

Hadoop QA commented on HDFS-5654:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply 
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12618264/HDFS-5654.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/10584/console |


This message was automatically generated.

> Add lock context support to FSNamesystemLock
> --------------------------------------------
>
>                 Key: HDFS-5654
>                 URL: https://issues.apache.org/jira/browse/HDFS-5654
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HDFS-5654.patch
>
>
> Supporting new methods of locking the namesystem, ie. coarse or fine-grain, 
> needs an api to manage the locks (or any object conforming to Lock interface) 
> held during access to the namespace.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to