accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-2802) Make per-service configuration easier
Date Tue, 04 Nov 2014 21:23:34 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Tubbs updated ACCUMULO-2802:
----------------------------------------
    Fix Version/s:     (was: 1.7.0)
                   2.0.0

> Make per-service configuration easier
> -------------------------------------
>
>                 Key: ACCUMULO-2802
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2802
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: gc, master, monitor, trace, tserver
>            Reporter: Christopher Tubbs
>             Fix For: 2.0.0
>
>
> Currently, all server configuration is stored in a monolithic xml file (accumulo-site.xml).
> We should support configuration scoped to the service it is intended to configure. That
means, that there could be a separate configuration file for each service (gc.conf, tserver.conf,
master.conf, monitor.conf, tracer.conf, etc.), which could be specified with a parameter to
the service's main method (--config <file>) with a sensible default.
> Some shared configuration may still be necessary, but that can be easily satisfied by
using commons-configuration, which supports include statements.
> Additionally, system properties should override the configuration file, and be interpolated
into it. This can be easily achieved with commons-configuration's hierarchical configuration.
> A monolithic file could still be supported, if the individual files are concatenated.
To ensure this is possible, the service-specific prefixes should remain, to distinguish between
the scopes.
> Any implementation of this should be backwards compatible with the monolithic accumulo-site.xml.
> Some benefits of this:
> # Consolidated configuration to a single file per service, instead of multiple command-line
parameters per service.
> # Allow non-XML configuration options.
> # Move away from Hadoop libraries for parsing configuration.
> # Allow starting multiple instances of the same service type with different configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message