You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@accumulo.apache.org by Jeff Kubina <je...@gmail.com> on 2016/10/05 00:21:47 UTC
setting tserver configs from the accumulo shell
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?
Re: setting tserver configs from the accumulo shell
Posted by Christopher <ct...@apache.org>.
At most, yes.
The properties which affect both would be the ones which start with
"general." or "instance.", with the latter being ones which must be the
same across the cluster in order for servers to participate in the same
cluster.
For all X, not in {general, instance}, properties starting with "X." should
only affect servers of type X. Otherwise, that's almost certainly a bug.
On Tue, Oct 4, 2016 at 9:21 PM Jeff Kubina <je...@gmail.com> wrote:
> So just to clarify, changing a tserver.* option would at most only
> require a restart of all the tservers, not a restart of the master?
>
>
> On Tue, Oct 4, 2016 at 9:14 PM, Christopher <ct...@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 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 <je...@gmail.com> 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 <ct...@apache.org> 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 <dl...@comcast.net> wrote:
>
> I don't think so.
>
> On Oct 4, 2016 8:21 PM, Jeff Kubina <je...@gmail.com> 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?
>
>
>
>
>
Re: setting tserver configs from the accumulo shell
Posted by Jeff Kubina <je...@gmail.com>.
So just to clarify, changing a tserver.* option would at most only require
a restart of all the tservers, not a restart of the master?
On Tue, Oct 4, 2016 at 9:14 PM, Christopher <ct...@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 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 <je...@gmail.com> 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 <ct...@apache.org> 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 <dl...@comcast.net> wrote:
>>
>> I don't think so.
>>
>> On Oct 4, 2016 8:21 PM, Jeff Kubina <je...@gmail.com> 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?
>>
>>
>>
>>
Re: setting tserver configs from the accumulo shell
Posted by Michael Wall <mj...@gmail.com>.
That is what I recall as well Josh. It is confusing for sure.
On Wed, Oct 5, 2016 at 11:57 AM, Josh Elser <jo...@gmail.com> wrote:
> IIRC, a property being mutable in ZooKeeper is disjoint from whether it
> will be dynamically reloaded.
>
> That is, a mutable ZK property does not imply that it is always
> dynamically picked up.
>
> Billie Rinaldi wrote:
>
>> 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 <ctubbsii@apache.org
>> <ma...@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 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 <jeff.kubina@gmail.com
>> <ma...@gmail.com>> 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 <tel:(410)%20988-4436>
>>
>>
>> On Tue, Oct 4, 2016 at 8:59 PM, Christopher <ctubbsii@apache.org
>> <ma...@apache.org>> 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 <dlmarion@comcast.net
>> <ma...@comcast.net>> wrote:
>>
>> I don't think so.
>>
>>
>> On Oct 4, 2016 8:21 PM, Jeff Kubina
>> <jeff.kubina@gmail.com <ma...@gmail.com>>
>> 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?
>>
>>
>>
>>
>>
Re: setting tserver configs from the accumulo shell
Posted by Josh Elser <jo...@gmail.com>.
Gotcha, Billie. I realize that I misinterpreted what you were saying
earlier :)
I think it would be good for us to annotate properties which are not
dynamically picked up instead of relying on "words". Hopefully it is
very few properties which are not dynamically updating by now (but I'm
not sure).
Billie Rinaldi wrote:
> Yes, we keep track of both pieces of information in Property and that is
> recorded in the user manual.
>
> On Wed, Oct 5, 2016 at 8:57 AM, Josh Elser <josh.elser@gmail.com
> <ma...@gmail.com>> wrote:
>
> IIRC, a property being mutable in ZooKeeper is disjoint from whether
> it will be dynamically reloaded.
>
> That is, a mutable ZK property does not imply that it is always
> dynamically picked up.
>
> Billie Rinaldi wrote:
>
> 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
> <http://accumulo.apache.org/1.8/accumulo_user_manual#_tserver_port_client>
>
> On Tue, Oct 4, 2016 at 6:14 PM, Christopher <ctubbsii@apache.org
> <ma...@apache.org>
> <mailto:ctubbsii@apache.org <ma...@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
> 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
> <jeff.kubina@gmail.com <ma...@gmail.com>
> <mailto:jeff.kubina@gmail.com <ma...@gmail.com>>>
> 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 <tel:410-988-4436> <tel:(410)%20988-4436>
>
>
> On Tue, Oct 4, 2016 at 8:59 PM, Christopher
> <ctubbsii@apache.org <ma...@apache.org>
> <mailto:ctubbsii@apache.org <ma...@apache.org>>> 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
> <dlmarion@comcast.net <ma...@comcast.net>
> <mailto:dlmarion@comcast.net <ma...@comcast.net>>> wrote:
>
> I don't think so.
>
>
> On Oct 4, 2016 8:21 PM, Jeff Kubina
> <jeff.kubina@gmail.com <ma...@gmail.com>
> <mailto:jeff.kubina@gmail.com <ma...@gmail.com>>>
> 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?
>
>
>
>
>
Re: setting tserver configs from the accumulo shell
Posted by Billie Rinaldi <bi...@gmail.com>.
Yes, we keep track of both pieces of information in Property and that is
recorded in the user manual.
On Wed, Oct 5, 2016 at 8:57 AM, Josh Elser <jo...@gmail.com> wrote:
> IIRC, a property being mutable in ZooKeeper is disjoint from whether it
> will be dynamically reloaded.
>
> That is, a mutable ZK property does not imply that it is always
> dynamically picked up.
>
> Billie Rinaldi wrote:
>
>> 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 <ctubbsii@apache.org
>> <ma...@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 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 <jeff.kubina@gmail.com
>> <ma...@gmail.com>> 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 <tel:(410)%20988-4436>
>>
>>
>> On Tue, Oct 4, 2016 at 8:59 PM, Christopher <ctubbsii@apache.org
>> <ma...@apache.org>> 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 <dlmarion@comcast.net
>> <ma...@comcast.net>> wrote:
>>
>> I don't think so.
>>
>>
>> On Oct 4, 2016 8:21 PM, Jeff Kubina
>> <jeff.kubina@gmail.com <ma...@gmail.com>>
>> 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?
>>
>>
>>
>>
>>
Re: setting tserver configs from the accumulo shell
Posted by Josh Elser <jo...@gmail.com>.
IIRC, a property being mutable in ZooKeeper is disjoint from whether it
will be dynamically reloaded.
That is, a mutable ZK property does not imply that it is always
dynamically picked up.
Billie Rinaldi wrote:
> 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 <ctubbsii@apache.org
> <ma...@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 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 <jeff.kubina@gmail.com
> <ma...@gmail.com>> 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 <tel:(410)%20988-4436>
>
>
> On Tue, Oct 4, 2016 at 8:59 PM, Christopher <ctubbsii@apache.org
> <ma...@apache.org>> 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 <dlmarion@comcast.net
> <ma...@comcast.net>> wrote:
>
> I don't think so.
>
>
> On Oct 4, 2016 8:21 PM, Jeff Kubina
> <jeff.kubina@gmail.com <ma...@gmail.com>>
> 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?
>
>
>
>
Re: setting tserver configs from the accumulo shell
Posted by Billie Rinaldi <bi...@gmail.com>.
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 <ct...@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 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 <je...@gmail.com> 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 <ct...@apache.org> 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 <dl...@comcast.net> wrote:
>>
>> I don't think so.
>>
>> On Oct 4, 2016 8:21 PM, Jeff Kubina <je...@gmail.com> 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?
>>
>>
>>
>>
Re: setting tserver configs from the accumulo shell
Posted by Christopher <ct...@apache.org>.
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 <je...@gmail.com> 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 <ct...@apache.org> 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 <dl...@comcast.net> wrote:
>
> I don't think so.
>
> On Oct 4, 2016 8:21 PM, Jeff Kubina <je...@gmail.com> 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?
>
>
>
>
Re: setting tserver configs from the accumulo shell
Posted by Jeff Kubina <je...@gmail.com>.
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
On Tue, Oct 4, 2016 at 8:59 PM, Christopher <ct...@apache.org> 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 <dl...@comcast.net> wrote:
>
>> I don't think so.
>>
>> On Oct 4, 2016 8:21 PM, Jeff Kubina <je...@gmail.com> 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?
>>
>>
>>
Re: setting tserver configs from the accumulo shell
Posted by Christopher <ct...@apache.org>.
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 <dl...@comcast.net> wrote:
> I don't think so.
>
> On Oct 4, 2016 8:21 PM, Jeff Kubina <je...@gmail.com> 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?
>
>
>