accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3412) Consistent application of runtime configuration changes
Date Fri, 12 Dec 2014 23:27:13 GMT

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

Sean Busbey commented on ACCUMULO-3412:
---------------------------------------

Sure, that'd be a fine implementation.

I just didn't want to limit the solution while describing the problem. I
know some folks previously stated a preference for those methods to remain
asynchronous.



> Consistent application of runtime configuration changes
> -------------------------------------------------------
>
>                 Key: ACCUMULO-3412
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3412
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: zookeeper
>    Affects Versions: 1.7.0
>            Reporter: Sean Busbey
>
> Right now changes to runtime configurable properties are lazily applied across the cluster.
Define stricter rules about when rules are in affect.
> * Minimal goal: allow for client notification when a configuration change has been applied
across the cluster.
> * Stretch: do something fancy so that we have consistent application across the cluster
(e.g. either all tablet servers are applying a constraint to a table or none are)



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

Mime
View raw message