Thanks for all the good info.
We have found that running drain first before restarting should always be
done, even if there is not much data or I/O.
Also, we've found that node tool drain returns often before it's finished,
so it's important to watch the logs (or opscenter) for it and any
compact
You might want to take a peek at what’s happening in the process via strace -p
or tcpdump. I can’t remember ever waiting an hour for a node to rejoin.
On Apr 25, 2014, at 8:59 AM, Tyler Hobbs wrote:
>
> On Fri, Apr 25, 2014 at 10:43 AM, Phil Burress
> wrote:
> Thanks. I made a change to a
On Fri, Apr 25, 2014 at 10:43 AM, Phil Burress wrote:
> Thanks. I made a change to a single node and it took almost an hour to
> rejoin the cluster (go from DN to UP in nodetool status). The cluster is
> pretty much idle right now and has a very small dataset. Is that normal?
Not unless it had t
Thanks. I made a change to a single node and it took almost an hour to
rejoin the cluster (go from DN to UP in nodetool status). The cluster is
pretty much idle right now and has a very small dataset. Is that normal?
On Fri, Apr 25, 2014 at 10:08 AM, Chris Lohfink wrote:
> Yes.
>
> Some changes
Yes.
Some changes you can manually have take affect without a restart (ie
compactionthroughput, things settable from jmx). There is also config changes
you cant really make like switching the snitch and such without a big todo.
---
Chris
On Apr 25, 2014, at 8:53 AM, Phil Burress wrote:
> If
If I wanted to make a configuration change to a single node in a cluster,
what is the recommended approach for doing that? Is it ok to just stop that
instance, make the change and then restart it?
