FAQ
Provide a way to specifiy login out side an RPC
-----------------------------------------------

Key: HADOOP-2683
URL: https://issues.apache.org/jira/browse/HADOOP-2683
Project: Hadoop
Issue Type: Bug
Reporter: Raghu Angadi
Priority: Blocker
Fix For: 0.16.0



Requirements AFIK :

It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.

Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.

Please include any other Jira's that depend on this.

Proposed fix:
- UserGroupInformation becomes an abstract class
- public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
- public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
- all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().



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

Search Discussions

  • Raghu Angadi (JIRA) at Jan 23, 2008 at 12:17 am
    [ https://issues.apache.org/jira/browse/HADOOP-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Raghu Angadi updated HADOOP-2683:
    ---------------------------------

    Component/s: dfs
    Description:
    Requirements AFIK :

    It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.

    Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.

    Please include any other Jira's that depend on this.

    Proposed fix:
    - UserGroupInformation becomes an abstract class
    - public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
    - public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
    - all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().



    was:

    Requirements AFIK :

    It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.

    Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.

    Please include any other Jira's that depend on this.

    Proposed fix:
    - UserGroupInformation becomes an abstract class
    - public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
    - public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
    - all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().



    Affects Version/s: 0.16.0
    Provide a way to specifiy login out side an RPC
    -----------------------------------------------

    Key: HADOOP-2683
    URL: https://issues.apache.org/jira/browse/HADOOP-2683
    Project: Hadoop
    Issue Type: Bug
    Components: dfs
    Affects Versions: 0.16.0
    Reporter: Raghu Angadi
    Priority: Blocker
    Fix For: 0.16.0


    Requirements AFIK :
    It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.
    Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.
    Please include any other Jira's that depend on this.
    Proposed fix:
    - UserGroupInformation becomes an abstract class
    - public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
    - public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
    - all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().
    --
    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 Jan 23, 2008 at 12:30 am
    [ https://issues.apache.org/jira/browse/HADOOP-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561531#action_12561531 ]

    Doug Cutting commented on HADOOP-2683:
    --------------------------------------

    UserGroupInformation should not become dependent on Server, rather, UserGroupInformation should own the ThreadLocal, and Server should be a client of that functionality.
    Provide a way to specifiy login out side an RPC
    -----------------------------------------------

    Key: HADOOP-2683
    URL: https://issues.apache.org/jira/browse/HADOOP-2683
    Project: Hadoop
    Issue Type: Bug
    Components: dfs
    Affects Versions: 0.16.0
    Reporter: Raghu Angadi
    Priority: Blocker
    Fix For: 0.16.0


    Requirements AFIK :
    It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.
    Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.
    Please include any other Jira's that depend on this.
    Proposed fix:
    - UserGroupInformation becomes an abstract class
    - public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
    - public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
    - all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Nigel Daley (JIRA) at Jan 23, 2008 at 12:49 am
    [ https://issues.apache.org/jira/browse/HADOOP-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Nigel Daley updated HADOOP-2683:
    --------------------------------

    Fix Version/s: (was: 0.16.0)
    0.17.0
    Provide a way to specifiy login out side an RPC
    -----------------------------------------------

    Key: HADOOP-2683
    URL: https://issues.apache.org/jira/browse/HADOOP-2683
    Project: Hadoop
    Issue Type: Bug
    Components: dfs
    Affects Versions: 0.16.0
    Reporter: Raghu Angadi
    Priority: Blocker
    Fix For: 0.17.0


    Requirements AFIK :
    It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.
    Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.
    Please include any other Jira's that depend on this.
    Proposed fix:
    - UserGroupInformation becomes an abstract class
    - public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
    - public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
    - all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().
    --
    This message is automatically generated by JIRA.
    -
    You can reply to this email to add a comment to the issue online.
  • Robert Chansler (JIRA) at Jan 25, 2008 at 11:28 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Robert Chansler reassigned HADOOP-2683:
    ---------------------------------------

    Assignee: Raghu Angadi
    Provide a way to specifiy login out side an RPC
    -----------------------------------------------

    Key: HADOOP-2683
    URL: https://issues.apache.org/jira/browse/HADOOP-2683
    Project: Hadoop Core
    Issue Type: Bug
    Components: dfs
    Affects Versions: 0.16.0
    Reporter: Raghu Angadi
    Assignee: Raghu Angadi
    Priority: Blocker
    Fix For: 0.17.0


    Requirements AFIK :
    It is required in some special cases (benchmarks etc) to invoke NameNode functionality without an RPC. For this users should be able to set user information that is otherwise available only an RPC.
    Patch for HADOOP-1298 includes a change to Server.java so that {{Server.getUserInfo()}} does not need to in an RPC. This probably will be replaced by patch here.
    Please include any other Jira's that depend on this.
    Proposed fix:
    - UserGroupInformation becomes an abstract class
    - public static UserGroupInformation.getUserInfo() is added. which usually just returns Server.getUserInfo();
    - public static UserGroupInformation.setUserInfo(UserGroupInformation) sets a thread local that will returned if Server.getUserInfo() returns null.
    - all invocations of Server.getUserInfo() will be replaced by UserGroupInformation.getUserInfo().
    --
    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
postedJan 23, '08 at 12:17a
activeJan 25, '08 at 11:28p
posts5
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Robert Chansler (JIRA): 5 posts

People

Translate

site design / logo © 2022 Grokbase