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-3411) Refactor VolumeManager initialization so a ServerConfigurationFactory is available
Date Thu, 27 Jul 2017 16:20:01 GMT

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

Christopher Tubbs updated ACCUMULO-3411:
----------------------------------------
    Fix Version/s: 2.0.0

> Refactor VolumeManager initialization so a ServerConfigurationFactory is available
> ----------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3411
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3411
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Sean Busbey
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> VolumeChooser would be improved by an init call that provided a ServerConfigurationFactory.
Currently, instances that need table configuration have to instantiate their own lazily.
> The initialization must be lazy because making their own instance requires an Instance
object. instantiating an HDFSZooInstance requires a VolumeManager. Since the VolumeManager
relies on their being a chooser, we get into a circular dependency.
> Either refactor VolumeManager instantiation so there is a ServerConfigurationFactory
that can be passed to the VolumeChooser or do bootstrapping with a VolumeManager that doesn't
use a VC to break the cycle.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message