[
https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640031#action_12640031
]
Hadoop QA commented on HADOOP-4398:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12392208/HADOOP-4398.1.txt
against trunk revision 705073.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 18 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 core tests. The patch passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3470/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3470/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3470/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3470/console
This message is automatically generated.
> fuse-dfs per FD context is not thread safe and can cause segfaults and
> corruptions
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-4398
> URL: https://issues.apache.org/jira/browse/HADOOP-4398
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/fuse-dfs
> Affects Versions: 0.20.0
> Reporter: Pete Wyckoff
> Assignee: Pete Wyckoff
> Fix For: 0.20.0
>
> Attachments: HADOOP-4398.1.txt
>
>
> this affects dfs_read and dfs_write and dfs_open dfs_release.
> people have seen corruptions in 0.18.1 on reads - hadoop-4397.
> In 0.19 since there is no global DFS handle, it is slightly different, but
> the same principles need to be applied and make the per FD context data (ie
> ptr to DFS, read buffer, ...) thread safe.
> I can't think of a way to add a reliable test case for this in the current
> framework, but should be sure to assert pre/post conditions wherever possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
