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 "Steve Loughran (JIRA)" <ji...@apache.org> on 2008/05/22 01:19:58 UTC
[jira] Created: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Retain cause of bind failure in Server.bind
-------------------------------------------
Key: HADOOP-3434
URL: https://issues.apache.org/jira/browse/HADOOP-3434
Project: Hadoop Core
Issue Type: Improvement
Components: dfs
Affects Versions: 0.18.0
Reporter: Steve Loughran
When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
at org.apache.hadoop.ipc.Server.bind(Server.java:168)
at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-3434:
-----------------------------------
Attachment: hadoop-3434.patch
patch the file to retain the exception text and trace
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-3434:
-----------------------------------
Status: Patch Available (was: Open)
retains the underlying cause for a bind failure during name node startup
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "lohit vijayarenu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lohit vijayarenu updated HADOOP-3434:
-------------------------------------
Hadoop Flags: [Reviewed]
+1 Looks good.
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598860#action_12598860 ]
Steve Loughran commented on HADOOP-3434:
----------------------------------------
The patch changes the output to :
Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022 : Address already in use
at org.apache.hadoop.ipc.Server.bind(Server.java:168)
at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
Caused by: 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.bind(Server.java:166)
I havent supplied a test; you'd need to bring up two data nodes listening on the same port to test it. I could add a test for this in my project.
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601474#action_12601474 ]
Hudson commented on HADOOP-3434:
--------------------------------
Integrated in Hadoop-trunk #509 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/509/])
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 0.18.0
>
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-3434:
----------------------------------
Resolution: Fixed
Fix Version/s: 0.18.0
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Steve
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Fix For: 0.18.0
>
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-3434) Retain cause of bind failure in
Server.bind
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas reassigned HADOOP-3434:
-------------------------------------
Assignee: Steve Loughran
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 0.18.0
>
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why; the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.