Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B6E8310D79 for ; Fri, 12 Dec 2014 23:01:13 +0000 (UTC) Received: (qmail 29945 invoked by uid 500); 12 Dec 2014 23:01:13 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 29907 invoked by uid 500); 12 Dec 2014 23:01:13 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 29884 invoked by uid 99); 12 Dec 2014 23:01:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 23:01:13 +0000 Date: Fri, 12 Dec 2014 23:01:13 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3412) Consistent application of runtime configuration changes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244943#comment-14244943 ] Josh Elser commented on ACCUMULO-3412: -------------------------------------- bq. allow for client notification when a configuration change has been applied across the cluster. I would think that it simpler to update the calls which change said configuration to block until the configuration is consistent across all (or the necessary) nodes. > 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)