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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/03/27 23:03:32 UTC
[jira] Created: (HADOOP-1164) TestReplicationPolicy doesn't use
port 0 for the NameNode
TestReplicationPolicy doesn't use port 0 for the NameNode
---------------------------------------------------------
Key: HADOOP-1164
URL: https://issues.apache.org/jira/browse/HADOOP-1164
Project: Hadoop
Issue Type: Bug
Components: test
Affects Versions: 0.12.3
Reporter: Owen O'Malley
Assigned To: Owen O'Malley
Fix For: 0.13.0
The TestReplicationPolicy test doesn't use mini-dfs and specifies a fixed port, so it can crash with address in use:
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:184)
at org.apache.hadoop.ipc.Server.<init>(Server.java:622)
at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
at org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
at org.apache.hadoop.dfs.NameNode.init(NameNode.java:181)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:207)
at org.apache.hadoop.dfs.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:36)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1164) TestReplicationPolicy doesn't use
port 0 for the NameNode
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-1164:
----------------------------------
Attachment: h1164.patch
This changes the port to be "0" which causes the system to pick a port.
> TestReplicationPolicy doesn't use port 0 for the NameNode
> ---------------------------------------------------------
>
> Key: HADOOP-1164
> URL: https://issues.apache.org/jira/browse/HADOOP-1164
> Project: Hadoop
> Issue Type: Bug
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.13.0
>
> Attachments: h1164.patch
>
>
> The TestReplicationPolicy test doesn't use mini-dfs and specifies a fixed port, so it can crash with address in use:
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:184)
> at org.apache.hadoop.ipc.Server.<init>(Server.java:622)
> at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
> at org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:181)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:207)
> at org.apache.hadoop.dfs.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:36)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1164) TestReplicationPolicy doesn't use
port 0 for the NameNode
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485593 ]
Hadoop QA commented on HADOOP-1164:
-----------------------------------
Integrated in Hadoop-Nightly #42 (See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/42/)
> TestReplicationPolicy doesn't use port 0 for the NameNode
> ---------------------------------------------------------
>
> Key: HADOOP-1164
> URL: https://issues.apache.org/jira/browse/HADOOP-1164
> Project: Hadoop
> Issue Type: Bug
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.13.0
>
> Attachments: h1164.patch
>
>
> The TestReplicationPolicy test doesn't use mini-dfs and specifies a fixed port, so it can crash with address in use:
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:184)
> at org.apache.hadoop.ipc.Server.<init>(Server.java:622)
> at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
> at org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:181)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:207)
> at org.apache.hadoop.dfs.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:36)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1164) TestReplicationPolicy doesn't use
port 0 for the NameNode
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1164:
---------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Owen!
> TestReplicationPolicy doesn't use port 0 for the NameNode
> ---------------------------------------------------------
>
> Key: HADOOP-1164
> URL: https://issues.apache.org/jira/browse/HADOOP-1164
> Project: Hadoop
> Issue Type: Bug
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.13.0
>
> Attachments: h1164.patch
>
>
> The TestReplicationPolicy test doesn't use mini-dfs and specifies a fixed port, so it can crash with address in use:
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:184)
> at org.apache.hadoop.ipc.Server.<init>(Server.java:622)
> at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
> at org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:181)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:207)
> at org.apache.hadoop.dfs.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:36)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-1164) TestReplicationPolicy doesn't use
port 0 for the NameNode
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484608 ]
Hadoop QA commented on HADOOP-1164:
-----------------------------------
+1, because http://issues.apache.org/jira/secure/attachment/12354353/h1164.patch applied and successfully tested against trunk revision http://svn.apache.org/repos/asf/lucene/hadoop/trunk/523072. Results are at http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch
> TestReplicationPolicy doesn't use port 0 for the NameNode
> ---------------------------------------------------------
>
> Key: HADOOP-1164
> URL: https://issues.apache.org/jira/browse/HADOOP-1164
> Project: Hadoop
> Issue Type: Bug
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.13.0
>
> Attachments: h1164.patch
>
>
> The TestReplicationPolicy test doesn't use mini-dfs and specifies a fixed port, so it can crash with address in use:
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:184)
> at org.apache.hadoop.ipc.Server.<init>(Server.java:622)
> at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
> at org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:181)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:207)
> at org.apache.hadoop.dfs.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:36)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-1164) TestReplicationPolicy doesn't use
port 0 for the NameNode
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-1164:
----------------------------------
Status: Patch Available (was: Open)
> TestReplicationPolicy doesn't use port 0 for the NameNode
> ---------------------------------------------------------
>
> Key: HADOOP-1164
> URL: https://issues.apache.org/jira/browse/HADOOP-1164
> Project: Hadoop
> Issue Type: Bug
> Components: test
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assigned To: Owen O'Malley
> Fix For: 0.13.0
>
> Attachments: h1164.patch
>
>
> The TestReplicationPolicy test doesn't use mini-dfs and specifies a fixed port, so it can crash with address in use:
> java.net.BindException: Address already in use
> at sun.nio.ch.Net.bind(Native Method)
> at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
> at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:184)
> at org.apache.hadoop.ipc.Server.<init>(Server.java:622)
> at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:323)
> at org.apache.hadoop.ipc.RPC.getServer(RPC.java:293)
> at org.apache.hadoop.dfs.NameNode.init(NameNode.java:181)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:207)
> at org.apache.hadoop.dfs.TestReplicationPolicy.<clinit>(TestReplicationPolicy.java:36)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.