hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 10210240...@fudan.edu.cn
Subject Re: [jira] [Commented] (HDFS-4525) Provide an API for knowing that whether file is closed or not.
Date Sun, 03 Mar 2013 13:03:13 GMT
hi, 
please let me know how to unsubscribe from this mailing list, thank you.


> -----Origin email-----
> From: "Hadoop QA (JIRA)" <jira@apache.org>
> Sent Time: Sunday, March 3, 2013
> To: hdfs-issues@hadoop.apache.org
> Cc: 
> Subject: [jira] [Commented] (HDFS-4525) Provide an API for knowing that whether file
is closed or not.
> 
> 
>     [ https://issues.apache.org/jira/browse/HDFS-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591494#comment-13591494
] 
> 
> Hadoop QA commented on HDFS-4525:
> ---------------------------------
> 
> {color:red}-1 overall{color}.  Here are the results of testing the latest attachment

>   http://issues.apache.org/jira/secure/attachment/12571569/HDFS-4525.patch
>   against trunk revision .
> 
>     {color:green}+1 @author{color}.  The patch does not contain any @author tags.
> 
>     {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.
> 
>   {color:red}-1 one of tests included doesn't have a timeout.{color}
> 
>     {color:green}+1 javac{color}.  The applied patch does not increase the total number
of javac compiler warnings.
> 
>     {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.
> 
>     {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.
> 
>     {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.
> 
>     {color:green}+1 release audit{color}.  The applied patch does not increase the total
number of release audit warnings.
> 
>     {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs.
> 
>     {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.
> 
> Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4029//testReport/
> Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4029//console
> 
> This message is automatically generated.
>                 
> > Provide an API for knowing that whether file is closed or not.
> > --------------------------------------------------------------
> >
> >                 Key: HDFS-4525
> >                 URL: https://issues.apache.org/jira/browse/HDFS-4525
> >             Project: Hadoop HDFS
> >          Issue Type: Sub-task
> >          Components: namenode
> >    Affects Versions: 3.0.0, 2.0.3-alpha
> >            Reporter: Uma Maheswara Rao G
> >            Assignee: SreeHari
> >         Attachments: HDFS-4525.patch
> >
> >
> > Currently recoverLease API will return true if file is already closed. Otherwise
it will trigger internalLease recovery and return false. It may take some time to really complete
this recovery and file to be closed completely. So, there is noway for the users to wait correctly
until file is closed completely. 
> > It would good if we have one API which says whether that file is closed or not.
So, that users can relay on that proceed further if and only if file is closed completely.
> > See the discussion in HBASE-7878
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira


Mime
View raw message