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 "lohit vijayarenu (JIRA)" <ji...@apache.org> on 2008/05/15 07:13:55 UTC
[jira] Created: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
-------------------------------------------------------------------------
Key: HADOOP-3393
URL: https://issues.apache.org/jira/browse/HADOOP-3393
Project: Hadoop Core
Issue Type: Bug
Components: dfs
Affects Versions: 0.18.0
Environment: LINUX, WINDOWS
Reporter: lohit vijayarenu
Fix For: 0.18.0
Attachments: HADOOP-HDFSServerPorts.patch
HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597022#action_12597022 ]
Hadoop QA commented on HADOOP-3393:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12382088/HADOOP-HDFSServerPorts.patch
against trunk revision 656491.
+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 tests are needed for this patch.
+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 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2476/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2476/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2476/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2476/console
This message is automatically generated.
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597461#action_12597461 ]
Hudson commented on HADOOP-3393:
--------------------------------
Integrated in Hadoop-trunk #493 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/493/])
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Assignee: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-3393:
----------------------------------
Resolution: Fixed
Assignee: lohit vijayarenu
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Lohit
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Assignee: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "lohit vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lohit vijayarenu updated HADOOP-3393:
-------------------------------------
Status: Patch Available (was: Open)
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "lohit vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597026#action_12597026 ]
lohit vijayarenu commented on HADOOP-3393:
------------------------------------------
Fixes test failure, does not include testcase.
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "lohit vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lohit vijayarenu updated HADOOP-3393:
-------------------------------------
Attachment: HADOOP-HDFSServerPorts.patch
This patch fixes the issue.
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3393) TestHDFSServerPorts fails on LINUX
(NFS mounted directory) and on WINDOWS
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597017#action_12597017 ]
Raghu Angadi commented on HADOOP-3393:
--------------------------------------
+1. The fix looks good.
> TestHDFSServerPorts fails on LINUX (NFS mounted directory) and on WINDOWS
> -------------------------------------------------------------------------
>
> Key: HADOOP-3393
> URL: https://issues.apache.org/jira/browse/HADOOP-3393
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Environment: LINUX, WINDOWS
> Reporter: lohit vijayarenu
> Fix For: 0.18.0
>
> Attachments: HADOOP-HDFSServerPorts.patch
>
>
> HADOOP-2656 changes the way BlockScanner and BlockScannerThread are created. TestHDFSServerPorts tries to create a DataNode object, but expects a failure while starting it. As part of creating DataNode object we create BlockScanner object but not its corresponding BlockScannerThread as Daemon. While in shutdown() we check if BlockScannerThread is not null, then call BlockScanner.shutdown() to close a reference to LogFile it holds.
> Now, on NFS mount and Windows, if a reference to file remains deleting the directory either leaves a .nfsXXXXX file or is not allowed (on windows). This was causing the test to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.