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/28 18:33:45 UTC
[jira] Created: (HADOOP-3458) StatusHttpServer should include
hostname/port when bind fails
StatusHttpServer should include hostname/port when bind fails
-------------------------------------------------------------
Key: HADOOP-3458
URL: https://issues.apache.org/jira/browse/HADOOP-3458
Project: Hadoop Core
Issue Type: Improvement
Components: mapred
Affects Versions: 0.18.0
Reporter: Steve Loughran
Priority: Minor
Just as server includes diagnostics on the host:port binding for a failed socket startup, we should catch and wrap any failure of jetty to start up with the same diagnostics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3458) StatusHttpServer should include
hostname/port when bind fails
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611164#action_12611164 ]
Steve Loughran commented on HADOOP-3458:
----------------------------------------
that was the wrong patch. I will create a new one when I get to the relevant machine
> StatusHttpServer should include hostname/port when bind fails
> -------------------------------------------------------------
>
> Key: HADOOP-3458
> URL: https://issues.apache.org/jira/browse/HADOOP-3458
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Priority: Minor
>
> Just as server includes diagnostics on the host:port binding for a failed socket startup, we should catch and wrap any failure of jetty to start up with the same diagnostics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3458) StatusHttpServer should include
hostname/port when bind fails
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-3458:
-----------------------------------
Status: Patch Available (was: Open)
Here is the patch that logs the host/port in use, it also handles a null host. I can write tests for this in our SVN repository; indeed -it is the default state when you bring up >1 job tracker in the same test, or try bringing two up one after the other, with no delay
> StatusHttpServer should include hostname/port when bind fails
> -------------------------------------------------------------
>
> Key: HADOOP-3458
> URL: https://issues.apache.org/jira/browse/HADOOP-3458
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: hadoop-3458.patch
>
>
> Just as server includes diagnostics on the host:port binding for a failed socket startup, we should catch and wrap any failure of jetty to start up with the same diagnostics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3458) StatusHttpServer should include
hostname/port when bind fails
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-3458:
-----------------------------------
Attachment: hadoop-3458.patch
patch for this
> StatusHttpServer should include hostname/port when bind fails
> -------------------------------------------------------------
>
> Key: HADOOP-3458
> URL: https://issues.apache.org/jira/browse/HADOOP-3458
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: hadoop-3458.patch
>
>
> Just as server includes diagnostics on the host:port binding for a failed socket startup, we should catch and wrap any failure of jetty to start up with the same diagnostics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3458) StatusHttpServer should include
hostname/port when bind fails
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-3458:
-----------------------------------
Attachment: (was: hadoop-3458.patch)
> StatusHttpServer should include hostname/port when bind fails
> -------------------------------------------------------------
>
> Key: HADOOP-3458
> URL: https://issues.apache.org/jira/browse/HADOOP-3458
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Priority: Minor
>
> Just as server includes diagnostics on the host:port binding for a failed socket startup, we should catch and wrap any failure of jetty to start up with the same diagnostics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3458) StatusHttpServer should include
hostname/port when bind fails
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated HADOOP-3458:
----------------------------------
Status: Open (was: Patch Available)
Would you mind explaining this in greater detail? The patch adds additional information to the message string for an assertion, but nothing is "logged." Since few run with assertions enabled, is this only in support of tests? I'm very confused at how the title of the JIRA, "we should catch and wrap any failure of jetty to start up with the same diagnostics," and the patch relate to one another.
> StatusHttpServer should include hostname/port when bind fails
> -------------------------------------------------------------
>
> Key: HADOOP-3458
> URL: https://issues.apache.org/jira/browse/HADOOP-3458
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: hadoop-3458.patch
>
>
> Just as server includes diagnostics on the host:port binding for a failed socket startup, we should catch and wrap any failure of jetty to start up with the same diagnostics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.