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 "Raghu Angadi (JIRA)" <ji...@apache.org> on 2009/03/16 20:47:50 UTC
[jira] Created: (HADOOP-5505) TestMissingBlocksAlert fails on 0.20.
TestMissingBlocksAlert fails on 0.20.
-------------------------------------
Key: HADOOP-5505
URL: https://issues.apache.org/jira/browse/HADOOP-5505
Project: Hadoop Core
Issue Type: Bug
Affects Versions: 0.20.0
Reporter: Raghu Angadi
Assignee: Raghu Angadi
Fix For: 0.20.0
TestMissingBlocksAlert fetches NameNode front page to verify that a an expected warning exists on the page.
The namenode here is part of a MiniDFSCluster and looks like JspHelper is not initialized properly when JVM has both a datanode and a NameNode.
Trunk is not affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-5505) TestMissingBlocksAlert fails on
0.20.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682487#action_12682487 ]
Raghu Angadi commented on HADOOP-5505:
--------------------------------------
Thanks Nicholas.
'ant test-core' is successful. I could not run 'test-patch' (it fails saying java5.home is not specified, though it is provided on the commandline). For this trivial fix, I think it is ok.
> TestMissingBlocksAlert fails on 0.20.
> -------------------------------------
>
> Key: HADOOP-5505
> URL: https://issues.apache.org/jira/browse/HADOOP-5505
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.20.0
>
> Attachments: HADOOP-5505-branch-20.patch
>
>
> TestMissingBlocksAlert fetches NameNode front page to verify that a an expected warning exists on the page.
> The namenode here is part of a MiniDFSCluster and looks like JspHelper is not initialized properly when JVM has both a datanode and a NameNode.
> Trunk is not affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5505) TestMissingBlocksAlert fails on 0.20.
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE updated HADOOP-5505:
-------------------------------------------
Component/s: dfs
Hadoop Flags: [Reviewed]
This problem is related to misuse of static variables (again). See also HADOOP-2413.
+1 patch looks good.
> TestMissingBlocksAlert fails on 0.20.
> -------------------------------------
>
> Key: HADOOP-5505
> URL: https://issues.apache.org/jira/browse/HADOOP-5505
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.20.0
>
> Attachments: HADOOP-5505-branch-20.patch
>
>
> TestMissingBlocksAlert fetches NameNode front page to verify that a an expected warning exists on the page.
> The namenode here is part of a MiniDFSCluster and looks like JspHelper is not initialized properly when JVM has both a datanode and a NameNode.
> Trunk is not affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-5505) TestMissingBlocksAlert fails on 0.20.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-5505:
---------------------------------
Attachment: HADOOP-5505-branch-20.patch
The attached patch fixes the initialization. This patch does not apply to trunk. I will run test-patch myself.
Thanks to Nicholas for help with tracking this.
> TestMissingBlocksAlert fails on 0.20.
> -------------------------------------
>
> Key: HADOOP-5505
> URL: https://issues.apache.org/jira/browse/HADOOP-5505
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.20.0
>
> Attachments: HADOOP-5505-branch-20.patch
>
>
> TestMissingBlocksAlert fetches NameNode front page to verify that a an expected warning exists on the page.
> The namenode here is part of a MiniDFSCluster and looks like JspHelper is not initialized properly when JVM has both a datanode and a NameNode.
> Trunk is not affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-5505) TestMissingBlocksAlert fails on
0.20.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi resolved HADOOP-5505.
----------------------------------
Resolution: Fixed
I just committed this.
> TestMissingBlocksAlert fails on 0.20.
> -------------------------------------
>
> Key: HADOOP-5505
> URL: https://issues.apache.org/jira/browse/HADOOP-5505
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.20.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Fix For: 0.20.0
>
> Attachments: HADOOP-5505-branch-20.patch
>
>
> TestMissingBlocksAlert fetches NameNode front page to verify that a an expected warning exists on the page.
> The namenode here is part of a MiniDFSCluster and looks like JspHelper is not initialized properly when JVM has both a datanode and a NameNode.
> Trunk is not affected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.