[ 
https://issues.apache.org/jira/browse/HADOOP-8574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408144#comment-13408144
 ] 

Guillaume Nodet commented on HADOOP-8574:
-----------------------------------------

Possible patch to kick the discussion: 
https://github.com/gnodet/hadoop-common/commit/742ab08aa068424fc2292cf1cd2d64a345053173
Though the OSGi metadata are not yet there, so this is not really testable yet 
(will upload a patch for that soon or JB).

There is one possibly controversial change which is the one in the 
Configuration (see 
https://github.com/gnodet/hadoop-common/commit/742ab08aa068424fc2292cf1cd2d64a345053173#L3R207).
The idea is that in OSGi, the whole configuration is controlled (at least the 
default) by ConfigAdmin.  The benefit is that clients don't really have to deal 
with configuration.  
One thing I haven't really understood is why the configuration isn't a global 
singleton (at least the defaults), as the configuration files are being read 
multiple times (each time a new configuration is created).


                
> Enable starting hadoop services from inside OSGi
> ------------------------------------------------
>
>                 Key: HADOOP-8574
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8574
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Guillaume Nodet
>
> This JIRA captures the needed things in order to start hadoop services in 
> OSGi.
> The main idea I used so far consists in:
>   * using the OSGi ConfigAdmin to store the hadoop configuration
>   * in that configuration, use a few boolean properties to determine which 
> services should be started (nameNode, dataNode ...)
>   * expose a configured url handler so that the whole OSGi runtime can use 
> urls in hdfs:/xxx
>   * the use of an OSGi ManagedService means that when the configuration 
> changes, the services will be stopped and restarted with the new configuration

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to