hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3574) Fix small race and do some cleanup in GetImageServlet
Date Tue, 03 Jul 2012 02:46:22 GMT

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

Hadoop QA commented on HDFS-3574:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 eclipse:eclipse.  The patch built with eclipse:eclipse.

    -1 findbugs.  The patch appears to introduce 2 new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed these unit tests in hadoop-common-project/hadoop-common


    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2731//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/2731//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2731//console

This message is automatically generated.
> Fix small race and do some cleanup in GetImageServlet
> -----------------------------------------------------
>                 Key: HDFS-3574
>                 URL: https://issues.apache.org/jira/browse/HDFS-3574
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 3.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>         Attachments: hdfs-3574.txt, hdfs-3574.txt, hdfs-3574.txt
> There's a very small race window in GetImageServlet, if the following interleaving occurs:
> - The Storage object returns some local file in the storage directory (eg an edits file
or image file)
> - *Race*: some other process removes the file
> - GetImageServlet calls file.length() which returns 0, since it doesn't exist. It thus
faithfully sets the Content-Length header to 0
> - getFileClient() throws FileNotFoundException when trying to open the file. But, since
we call response.getOutputStream() before this, the headers have already been sent, so we
fail to send the "404" or "500" response that we should.
> Thus, the client sees a 0-length Content-Length followed by 0 lengths of content, and
thinks it successfully has downloaded the target file, where in fact it downloads an empty
> I saw this in practice during the "edits synchronization" phase of recovery while working
on HDFS-3077, though it could apply on existing code paths, as well, I believe.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message