The second node will fail to start because of concurrent movement concerns
There’s a flag to override this if you know when it’s safe (for advanced users
only)
--
Jeff Jirsa
> On Apr 28, 2018, at 3:10 AM, Jinhua Luo wrote:
>
> HI All,
>
> For example, if at the same time, two nodes joining
Seed node takes care of token re-assignment. But why do you even wanna do that?
Add the node first and then remove.
Sent from my iPhone
> On Apr 28, 2018, at 5:10 AM, Jinhua Luo wrote:
>
> HI All,
>
> For example, if at the same time, two nodes joining and there nodes removing.
> How c* handl
Thanks, everybody.
Setting compaction throughput improved compaction performance. On
overloaded cluster number of SSTables dropped from ~16K to ~7K. This way I
can wait until it will be stabilized.
PS
This task is a one time process - I am upgrading Elasticsearch from v2 to
v6 and once I have same
HI All,
For example, if at the same time, two nodes joining and there nodes removing.
How c* handles such case? c* uses gossip to determine membership, and
it does not have central leader to serialize the membership changes.
-
To
If two DC are separated at first place before they meet each other.
And given the total token range is 100, and each DC has same tokens,
let's say 5.
Then because they assign tokens independently, they will has same
token ranges, right?
For example,
DC1 = {0, 20, 40, 60, 80}
DC2 = {0, 20, 40, 60, 8
