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 "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/06/11 07:39:25 UTC
[jira] Created: (HADOOP-1482) SecondaryNameNode does not roll ports
SecondaryNameNode does not roll ports
-------------------------------------
Key: HADOOP-1482
URL: https://issues.apache.org/jira/browse/HADOOP-1482
Project: Hadoop
Issue Type: Bug
Components: dfs
Reporter: dhruba borthakur
Assignee: dhruba borthakur
The SecondaryNamenode does not roll the port specified as dfs.secondary.info.port. This could cause unit tests to fail if an instance of ScondaryNameNode is already running on the test machine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1482) SecondaryNameNode does not roll ports
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1482:
---------------------------------
Resolution: Fixed
Fix Version/s: 0.14.0
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Dhruba!
> SecondaryNameNode does not roll ports
> -------------------------------------
>
> Key: HADOOP-1482
> URL: https://issues.apache.org/jira/browse/HADOOP-1482
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.14.0
>
> Attachments: SecondaryPortroll.patch
>
>
> The SecondaryNamenode does not roll the port specified as dfs.secondary.info.port. This could cause unit tests to fail if an instance of ScondaryNameNode is already running on the test machine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1482) SecondaryNameNode does not roll ports
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1482:
-------------------------------------
Attachment: SecondaryPortroll.patch
Make the Secondary info port settings roll from one number to another.
> SecondaryNameNode does not roll ports
> -------------------------------------
>
> Key: HADOOP-1482
> URL: https://issues.apache.org/jira/browse/HADOOP-1482
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: SecondaryPortroll.patch
>
>
> The SecondaryNamenode does not roll the port specified as dfs.secondary.info.port. This could cause unit tests to fail if an instance of ScondaryNameNode is already running on the test machine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1482) SecondaryNameNode does not roll ports
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1482:
-------------------------------------
Status: Patch Available (was: Open)
> SecondaryNameNode does not roll ports
> -------------------------------------
>
> Key: HADOOP-1482
> URL: https://issues.apache.org/jira/browse/HADOOP-1482
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: SecondaryPortroll.patch
>
>
> The SecondaryNamenode does not roll the port specified as dfs.secondary.info.port. This could cause unit tests to fail if an instance of ScondaryNameNode is already running on the test machine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1482) SecondaryNameNode does not roll
ports
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503960 ]
Hadoop QA commented on HADOOP-1482:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12359385/SecondaryPortroll.patch applied and successfully tested against trunk revision r546320.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/271/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/271/console
> SecondaryNameNode does not roll ports
> -------------------------------------
>
> Key: HADOOP-1482
> URL: https://issues.apache.org/jira/browse/HADOOP-1482
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: SecondaryPortroll.patch
>
>
> The SecondaryNamenode does not roll the port specified as dfs.secondary.info.port. This could cause unit tests to fail if an instance of ScondaryNameNode is already running on the test machine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1482) SecondaryNameNode does not roll
ports
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505462 ]
Hadoop QA commented on HADOOP-1482:
-----------------------------------
Integrated in Hadoop-Nightly #123 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/123/])
> SecondaryNameNode does not roll ports
> -------------------------------------
>
> Key: HADOOP-1482
> URL: https://issues.apache.org/jira/browse/HADOOP-1482
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.14.0
>
> Attachments: SecondaryPortroll.patch
>
>
> The SecondaryNamenode does not roll the port specified as dfs.secondary.info.port. This could cause unit tests to fail if an instance of ScondaryNameNode is already running on the test machine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.