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 "Arun C Murthy (JIRA)" <ji...@apache.org> on 2009/05/05 20:07:30 UTC

[jira] Created: (HADOOP-5772) Implement a 'refreshable' configuration system with right access-controls etc.

Implement a 'refreshable' configuration system with right access-controls etc.
------------------------------------------------------------------------------

                 Key: HADOOP-5772
                 URL: https://issues.apache.org/jira/browse/HADOOP-5772
             Project: Hadoop Core
          Issue Type: New Feature
          Components: conf
            Reporter: Arun C Murthy


We have various bits and pieces of code to refresh certain configuration files, various components to restrict access to who can actually refresh the configs etc. 

I propose we start thinking about a simple system to support this as a first-class citizen in Hadoop Core...

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


[jira] Commented: (HADOOP-5772) Implement a 'refreshable' configuration system with right access-controls etc.

Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706143#action_12706143 ] 

Jeff Hammerbacher commented on HADOOP-5772:
-------------------------------------------

Hey Arun,

https://issues.apache.org/jira/browse/HADOOP-5670 seems to address this issue as well. Should we consolidate discussion into one ticket?

Later,
Jeff

> Implement a 'refreshable' configuration system with right access-controls etc.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5772
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Arun C Murthy
>
> We have various bits and pieces of code to refresh certain configuration files, various components to restrict access to who can actually refresh the configs etc. 
> I propose we start thinking about a simple system to support this as a first-class citizen in Hadoop Core...

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


[jira] Commented: (HADOOP-5772) Implement a 'refreshable' configuration system with right access-controls etc.

Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706802#action_12706802 ] 

Steve Loughran commented on HADOOP-5772:
----------------------------------------

Incidentally, as I struggle to bring up a cluster where no machine knows their hostname/IPAddr until they have opened their IPC and http ports, it would be very good for the worker nodes -TT and DN- to be tweaked to reread the conf file every time they try looking up the address:port of the master nodes. That would allow the namenode and job tracker to restart on different hosts and have all the workers bond to them once their configurations are updated. 

> Implement a 'refreshable' configuration system with right access-controls etc.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5772
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Arun C Murthy
>
> We have various bits and pieces of code to refresh certain configuration files, various components to restrict access to who can actually refresh the configs etc. 
> I propose we start thinking about a simple system to support this as a first-class citizen in Hadoop Core...

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


[jira] Commented: (HADOOP-5772) Implement a 'refreshable' configuration system with right access-controls etc.

Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706372#action_12706372 ] 

Steve Loughran commented on HADOOP-5772:
----------------------------------------

I think reloading is separate from distributed sourcing of configuration . You can have a distributed source of configuration that isn't reloaded/read-on-demand; you can even reload stuff from the local (or NFS-mounted) FS

> Implement a 'refreshable' configuration system with right access-controls etc.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5772
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Arun C Murthy
>
> We have various bits and pieces of code to refresh certain configuration files, various components to restrict access to who can actually refresh the configs etc. 
> I propose we start thinking about a simple system to support this as a first-class citizen in Hadoop Core...

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


[jira] Commented: (HADOOP-5772) Implement a 'refreshable' configuration system with right access-controls etc.

Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706195#action_12706195 ] 

Arun C Murthy commented on HADOOP-5772:
---------------------------------------

Sure, alternatively we could use this jira to track just the 'refreshable' part of the configuration alongwith access-control etc.

> Implement a 'refreshable' configuration system with right access-controls etc.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5772
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Arun C Murthy
>
> We have various bits and pieces of code to refresh certain configuration files, various components to restrict access to who can actually refresh the configs etc. 
> I propose we start thinking about a simple system to support this as a first-class citizen in Hadoop Core...

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