Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 027DC200B99 for ; Wed, 5 Oct 2016 17:13:39 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 001F0160ADE; Wed, 5 Oct 2016 15:13:39 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1075F160ADB for ; Wed, 5 Oct 2016 17:13:37 +0200 (CEST) Received: (qmail 45548 invoked by uid 500); 5 Oct 2016 15:13:31 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 45538 invoked by uid 99); 5 Oct 2016 15:13:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2016 15:13:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 48EA71805DB for ; Wed, 5 Oct 2016 15:13:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 7hcszlUrEXHw for ; Wed, 5 Oct 2016 15:13:30 +0000 (UTC) Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id EB6B15F399 for ; Wed, 5 Oct 2016 15:13:29 +0000 (UTC) Received: by mail-oi0-f51.google.com with SMTP id m72so104941265oik.3 for ; Wed, 05 Oct 2016 08:13:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ISu2XKwqNRl86Zd3ImIuWqd4DLMxXFbPbVVP3Qxov2Y=; b=oL4w7hQ6SPhKoI9jEtn1n9kJBbC/f5MqdnULxudHWnAVgEOSXbVPXZcFgesTIW7DXq n8dsArN8bYtyBcel1zdGwFjeQy4GURdCxKF3nu7mNMtBbDJ/bCzho6TucHqFLpudm/nL OcHwdvAMmNdteF6jr003LnxCkUuLqhMcqF/Pl/IeQf2PLQJGv3I/amxrWsWV8FOTrzgR fX5dYry04KK9Pn/Qp2YugzVurwHDmhO9VSeg2XBOzLOwpaLLdPI+7PgLFCvErtwmFr4G vr4Rz4NgXKRURDCROxBmKhA7WVcjk94jH9jY9ubb56HqObpZLlZwajagcb2jTfJakF56 TYAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ISu2XKwqNRl86Zd3ImIuWqd4DLMxXFbPbVVP3Qxov2Y=; b=gkcisM7Xuf54PohVMSupVpTGdKriksAY/+EhN2aPBBUUAIHT6PnyXo0fAqTIr/BOKO J+kqEBvkW5UQMniRSwrzyUVezf9yoCE2ezZP1zwjqjDixxKeDNRLlqyHNEqAzI5NhUOj tes/StMWzepUGdDonklr1pbLvi0RujWg48eRYwBrqNJ4VVI8InIInCdOzz1AvAWPgWKM izjKzgRx6jniDc1i/5G9MwhvJ8UoK+CTuUpKVtZk4bitiItvdPp9VlBaSNgHL7lWGs4S t5avDk+0syYbS+TJc64KC9crZuOQrUIv5I/0JQjrOglocrUzzB9dAFCFHPm4Ue1lELKk PDYA== X-Gm-Message-State: AA6/9RmlrOsjGb55+gHYua61x3b2TLPWz/YTZatLuWC+Cpd4p3PCylJXI9dwit3dTSE5NtecpYQjylA7zIDOTw== X-Received: by 10.107.180.208 with SMTP id d199mr10002041iof.36.1475680409020; Wed, 05 Oct 2016 08:13:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.48.1 with HTTP; Wed, 5 Oct 2016 08:13:28 -0700 (PDT) In-Reply-To: References: <2cd8b293-a015-4c11-a429-2696331cecd6@email.android.com> From: Billie Rinaldi Date: Wed, 5 Oct 2016 08:13:28 -0700 Message-ID: Subject: Re: setting tserver configs from the accumulo shell To: "user@accumulo.apache.org" Content-Type: multipart/alternative; boundary=94eb2c05a1b494f820053e1f9ea1 archived-at: Wed, 05 Oct 2016 15:13:39 -0000 --94eb2c05a1b494f820053e1f9ea1 Content-Type: text/plain; charset=UTF-8 We already keep track of this in the Property class, whether a property can be changed in ZooKeeper and whether it requires a restart. Perhaps the information has grown stale, though. The information is exposed in the user manual: http://accumulo.apache.org/1.8/accumulo_user_manual#_tserver_port_client On Tue, Oct 4, 2016 at 6:14 PM, Christopher wrote: > Right now, I think you'd probably have to track down where that particular > property is used in the code to determine its lifecycle. I think it's going > to take some work to wrangle these into discrete sets for documentation > purposes, in the shell or otherwise. Some properties are only used during > certain times early in the server's lifecycle. Other properties are used on > demand. Some of those on demand properties are probably cached into > internal state for indefinite periods of time. It's hard to say which are > which without investigating each property individually (or through > empirical testing). > > On Tue, Oct 4, 2016 at 9:04 PM Jeff Kubina wrote: > >> That would be very helpful, but a note in the documentation would be fine >> initially. Is there an easy way to determine this from the source code? >> >> -- >> Jeff Kubina >> 410-988-4436 <(410)%20988-4436> >> >> >> On Tue, Oct 4, 2016 at 8:59 PM, Christopher wrote: >> >> Some do, some don't. One thing we could add to the shell is a >> notification that a restart is necessary for a particular change. Possibly. >> >> On Tue, Oct 4, 2016, 20:25 Dave wrote: >> >> I don't think so. >> >> On Oct 4, 2016 8:21 PM, Jeff Kubina wrote: >> >> Does changing the values of tserver configs in the accumulo shell, like >> "config -s tserver.server.threads.minimum=256", require a restart of all >> the tservers to become effective? >> >> >> >> --94eb2c05a1b494f820053e1f9ea1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We already keep track of this in the Property class, wheth= er a property can be changed in ZooKeeper and whether it requires a restart= . Perhaps the information has grown stale, though. The information is expos= ed in the user manual: http://accumulo.apache.org/1.8/accumulo_us= er_manual#_tserver_port_client

=
On Tue, Oct 4, 2016 at 6:14 PM, Christopher <= ctubbsii@apache.org> wrote:
Right now, I think you'd probably have to track down = where that particular property is used in the code to determine its lifecyc= le. I think it's going to take some work to wrangle these into discrete= sets for documentation purposes, in the shell or otherwise. Some propertie= s are only used during certain times early in the server's lifecycle. O= ther properties are used on demand. Some of those on demand properties are = probably cached into internal state for indefinite periods of time. It'= s hard to say which are which without investigating each property individua= lly (or through empirical testing).

On Tue, Oct 4, 2016= at 9:04 PM Jeff Kubina <jeff.kubina@gmail.com> wrote:
Tha= t would be very helpful, but a note in the documentation would be fine init= ially. Is there an easy way to determine this from the source code?

=
--=C2=A0
Jeff Kubina
410-988-4436

On Tue, Oct 4, 2016 at 8:59 PM, Christopher <ctubbsii@apache.org> wrote:

Some do, some= don't. One thing we could add to the shell is a notification that a re= start is necessary for a particular change. Possibly.


On Tue, Oct 4, 2016, 20:25 Dave <dlma= rion@comcast.net> wrote:

I don't think so.


On Oct 4, 2016 8:21 PM, Jeff Kubina <jeff.kubina@gmail.com> wrote:
Does changing the values of tserver configs in the accumulo shell, like = "config -s tserver.server.threads.minimum=3D256", require a = restart of all the tservers to become effective?



--94eb2c05a1b494f820053e1f9ea1--