FAQ
Need a way to get the inforserver port of a name node
-----------------------------------------------------

Key: HADOOP-4324
URL: https://issues.apache.org/jira/browse/HADOOP-4324
Project: Hadoop Core
Issue Type: New Feature
Components: dfs
Affects Versions: 0.20.0
Reporter: Steve Loughran
Assignee: Steve Loughran
Priority: Minor


To test that services shut down cleanly, I need to know the port that the namenode brings up an info server on, which means that its assigned port value needs to be exported from the namesystem.

I can see two ways to do this, and wish some recommendations of the best approach

1. extract the port value when the FSNameSystem comes up, and add it to that classes Conf; add a method to get that Conf so that its state can be read.
2. save the port value to a member variable in FSNameSystem and provide a public method to get at it.

My preference is for #1, as it is consistent with how the NameNode saves its port value, and doesn't change any APIs.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Search Discussions

  • Steve Loughran (JIRA) at Oct 1, 2008 at 4:00 pm
    [ https://issues.apache.org/jira/browse/HADOOP-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Steve Loughran resolved HADOOP-4324.
    ------------------------------------

    Resolution: Invalid

    looking in the wrong place; getInfoPort() does it. It may still be useful to push out to the Conf instance though.
    Need a way to get the inforserver port of a name node
    -----------------------------------------------------

    Key: HADOOP-4324
    URL: https://issues.apache.org/jira/browse/HADOOP-4324
    Project: Hadoop Core
    Issue Type: New Feature
    Components: dfs
    Affects Versions: 0.20.0
    Reporter: Steve Loughran
    Assignee: Steve Loughran
    Priority: Minor

    To test that services shut down cleanly, I need to know the port that the namenode brings up an info server on, which means that its assigned port value needs to be exported from the namesystem.
    I can see two ways to do this, and wish some recommendations of the best approach
    1. extract the port value when the FSNameSystem comes up, and add it to that classes Conf; add a method to get that Conf so that its state can be read.
    2. save the port value to a member variable in FSNameSystem and provide a public method to get at it.
    My preference is for #1, as it is consistent with how the NameNode saves its port value, and doesn't change any APIs.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Doug Cutting (JIRA) at Oct 1, 2008 at 5:24 pm
    [ https://issues.apache.org/jira/browse/HADOOP-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636102#action_12636102 ]

    Doug Cutting commented on HADOOP-4324:
    --------------------------------------

    I'm generally not a fan of using the Configuration for output. A Configuration is a generic input mechanism for metadata, not a read/write blackboard for state.
    Need a way to get the inforserver port of a name node
    -----------------------------------------------------

    Key: HADOOP-4324
    URL: https://issues.apache.org/jira/browse/HADOOP-4324
    Project: Hadoop Core
    Issue Type: New Feature
    Components: dfs
    Affects Versions: 0.20.0
    Reporter: Steve Loughran
    Assignee: Steve Loughran
    Priority: Minor

    To test that services shut down cleanly, I need to know the port that the namenode brings up an info server on, which means that its assigned port value needs to be exported from the namesystem.
    I can see two ways to do this, and wish some recommendations of the best approach
    1. extract the port value when the FSNameSystem comes up, and add it to that classes Conf; add a method to get that Conf so that its state can be read.
    2. save the port value to a member variable in FSNameSystem and provide a public method to get at it.
    My preference is for #1, as it is consistent with how the NameNode saves its port value, and doesn't change any APIs.
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedOct 1, '08 at 1:04p
activeOct 1, '08 at 5:24p
posts3
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Doug Cutting (JIRA): 3 posts

People

Translate

site design / logo © 2022 Grokbase