You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Pete Wyckoff (JIRA)" <ji...@apache.org> on 2008/10/13 02:50:44 UTC
[jira] Created: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
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.19.0
Reporter: Pete Wyckoff
Fix For: 0.19.0
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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Attachment: HADOOP-4398.2.txt
fixed comments.
> 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, HADOOP-4398.2.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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Status: Open (was: Patch Available)
> 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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Attachment: HADOOP-4398.1.txt
this patch fixes all threading issues
> 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
> 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.
[jira] Commented: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640400#action_12640400 ]
Pete Wyckoff commented on HADOOP-4398:
--------------------------------------
ready to commit as the test failure had nothing to do with fuse-dfs.
> 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, HADOOP-4398.2.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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Assignee: Pete Wyckoff
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Resolved: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff resolved HADOOP-4398.
----------------------------------
Resolution: Duplicate
duplicate of 0.19 JIRA 4399 for the same issue.
> 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, HADOOP-4398.2.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.
[jira] Commented: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Zheng Shao (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640394#action_12640394 ]
Zheng Shao commented on HADOOP-4398:
------------------------------------
+1
Talked with Pete. Looks good to me.
> 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, HADOOP-4398.2.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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Status: Open (was: Patch Available)
> 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, HADOOP-4398.2.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.
[jira] Commented: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640383#action_12640383 ]
Hadoop QA commented on HADOOP-4398:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12392300/HADOOP-4398.2.txt
against trunk revision 705215.
+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 failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3478/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3478/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3478/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3478/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, HADOOP-4398.2.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.
[jira] Commented: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640384#action_12640384 ]
Pete Wyckoff commented on HADOOP-4398:
--------------------------------------
core test failure not due to this patch as fuse-dfs is not accessed in any way by any of those tests
> 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, HADOOP-4398.2.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.
[jira] Commented: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640870#action_12640870 ]
Hudson commented on HADOOP-4398:
--------------------------------
Integrated in Hadoop-trunk #637 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/637/])
. No need to truncate access time in INode. Also fixes NPE
in CreateEditsLog. (Raghu Angadi)
> 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, HADOOP-4398.2.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.
[jira] Commented: (HADOOP-4398) fuse-dfs per FD context is not
thread safe and can cause segfaults and corruptions
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-4398) fuse-dfs per FD context is not thread
safe and can cause segfaults and corruptions
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-4398:
---------------------------------
Affects Version/s: (was: 0.19.0)
0.20.0
Fix Version/s: (was: 0.19.0)
0.20.0
> 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
> Fix For: 0.20.0
>
>
> 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.