hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1596) Create service endpoint to download configuration from SCM
Date Wed, 28 Aug 2019 16:23:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1596?focusedWorklogId=303016&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-303016
]

ASF GitHub Bot logged work on HDDS-1596:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Aug/19 16:22
            Start Date: 28/Aug/19 16:22
    Worklog Time Spent: 10m 
      Work Description: anuengineer commented on issue #861: HDDS-1596. Create service endpoint
to download configuration from SCM
URL: https://github.com/apache/hadoop/pull/861#issuecomment-525819238
 
 
   Done, committed in the trunk.
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 303016)
    Time Spent: 4h  (was: 3h 50m)

> Create service endpoint to download configuration from SCM
> ----------------------------------------------------------
>
>                 Key: HDDS-1596
>                 URL: https://issues.apache.org/jira/browse/HDDS-1596
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> As written in the design doc (see the parent issue) it was proposed to download the configuration
from the scm by the other services.
> I propose to create a separated endpoint to provide the ozone configuration. /conf can't
be used as it contains *all* the configuration and we need only the modified configuration.
> The easiest way to implement this feature is:
>  * Create a simple rest endpoint which publishes all the configuration
>  * Download the configurations to $HADOOP_CONF_DIR/ozone-global.xml during the service
startup.
>  * Add ozone-global.xml as an additional config source (before ozone-site.xml but after
ozone-default.xml)
>  * The download can be optional
> With this approach we keep the support of the existing manual configuration (ozone-site.xml
has higher priority) but we can download the configuration to a separated file during the
startup, which will be loaded.
> There is no magic: the configuration file is saved and it's easy to debug what's going
on as the OzoneConfiguration is loaded from the $HADOOP_CONF_DIR as before.
> Possible follow-up steps:
>  * Migrate all the other services (recon, s3g) to the new approach. (possible newbie
jiras)
>  * Improve the CLI to define the SCM address. (As of now we use ozone.scm.names)
>  * Create a service/hostname registration mechanism and autofill some of the configuration
based on the topology information.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message