Re: Nodes show different number of tokens than initially

On Fri, Feb 2, 2018 at 2:37 AM, kurt greaves wrote: > So one time I tried to understand why only a single node could have a > token, and it appeared that it came over the fence from facebook and has > been kept ever since. Personally I don't think it's necessary, and agree

Re: Nodes show different number of tokens than initially

So one time I tried to understand why only a single node could have a token, and it appeared that it came over the fence from facebook and has been kept ever since. Personally I don't think it's necessary, and agree that it is kind of problematic (but there's probably lot's of stuff that relies on

Re: Nodes show different number of tokens than initially

On Thu, Feb 1, 2018 at 5:19 AM, Jeff Jirsa wrote: > >> The reason I find it surprising, is that it makes very little *sense* to >> put a token belonging to a mode from one DC between tokens of nodes from >> another one. >> > > I don't want to really turn this into an argument

Re: Nodes show different number of tokens than initially

> > I don’t know why this is a surprise (maybe because people like to talk > about multiple rings, but the fact that replication strategy is set per > keyspace and that you could use SimpleStrategy in a multiple dc cluster > demonstrates this), but we can chat about that another time This is

Re: Nodes show different number of tokens than initially

On Wed, Jan 31, 2018 at 12:08 PM, Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On 31 Jan 2018 17:18, "Jeff Jirsa" wrote: > > > I don’t know why this is a surprise (maybe because people like to talk > about multiple rings, but the fact that replication strategy is

Re: Nodes show different number of tokens than initially

On 31 Jan 2018 17:18, "Jeff Jirsa" wrote: I don’t know why this is a surprise (maybe because people like to talk about multiple rings, but the fact that replication strategy is set per keyspace and that you could use SimpleStrategy in a multiple dc cluster demonstrates this),

Re: Nodes show different number of tokens than initially

> On Jan 31, 2018, at 12:35 AM, Oleksandr Shulgin > wrote: > >> On Tue, Jan 30, 2018 at 5:44 PM, Jeff Jirsa wrote: >> All DCs in a cluster use the same token space in the DHT, > > I can't believe my bloody eyes, but this seems to be true...

Re: Nodes show different number of tokens than initially

So the only reason that the new node would "steal" the token is if it started up earlier - which is based off how many heartbeats have occurred since entering NORMAL status on each node. I can't see any reason the new nodes would have higher generation numbers, so sounds likely there's a bug

Re: Nodes show different number of tokens than initially

On Wed, Jan 31, 2018 at 5:06 AM, Dikang Gu wrote: > What's the partitioner you use? We have logic to prevent duplicate tokens. > We are using the default Murmur3Partitioner. The problem arises from the fact that we manually allocating the tokens as described earlier. --

Re: Nodes show different number of tokens than initially

On Tue, Jan 30, 2018 at 5:44 PM, Jeff Jirsa wrote: > All DCs in a cluster use the same token space in the DHT, > I can't believe my bloody eyes, but this seems to be true... so token conflicts across datacenters are invalid config > If this is deemed invalid config why does

Re: Nodes show different number of tokens than initially

What's the partitioner you use? We have logic to prevent duplicate tokens. private static Collection adjustForCrossDatacenterClashes(final TokenMetadata tokenMetadata, StrategyAdapter strategy, Collection tokens) { List filtered = Lists.newArrayListWithCapacity(tokens.size()); for

Re: Nodes show different number of tokens than initially

All DCs in a cluster use the same token space in the DHT, so token conflicts across datacenters are invalid config -- Jeff Jirsa > On Jan 29, 2018, at 11:50 PM, Oleksandr Shulgin > wrote: > >> On Tue, Jan 30, 2018 at 5:13 AM, kurt greaves

Re: Nodes show different number of tokens than initially

On Tue, Jan 30, 2018 at 5:13 AM, kurt greaves wrote: > Shouldn't happen. Can you send through nodetool ring output from one of > those nodes? Also, did the logs have anything to say about tokens when you > started the 3 seed nodes?​ > Hi Kurt, I cannot run nodetool ring

Re: Nodes show different number of tokens than initially

Shouldn't happen. Can you send through nodetool ring output from one of those nodes? Also, did the logs have anything to say about tokens when you started the 3 seed nodes?​

Re: Nodes show different number of tokens than initially

On Fri, Jan 26, 2018 at 3:08 PM, Kenneth Brotman < kenbrot...@yahoo.com.invalid> wrote: > > > Could it be that after distributing the data, some of the nodes did not > need to have a fourth token? > I'm not sure, but that would be definitely against my understanding of how token assignment

RE: Nodes show different number of tokens than initially

Oleksandr, Could it be that after distributing the data, some of the nodes did not need to have a fourth token? Kenneth Brotman From: Oleksandr Shulgin [mailto:oleksandr.shul...@zalando.de] Sent: Thursday, January 25, 2018 3:44 AM To: User Subject: Nodes show different number

Nodes show different number of tokens than initially

Hello, While testing token allocation with version 3.0.15 we are experiencing some quite unexpected result. We have deployed a secondary virtual DC with 6 nodes, 4 tokens per node. Then we were adding the 7th node to the new DC in order to observe the effect of ownership re-distribution. To set