I see what you are saying. So basically take whatever existing token I have and divide it by 2, give or take a couple of tokens?
On Mon, Feb 9, 2015 at 5:17 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Mon, Feb 9, 2015 at 4:59 PM, Seth Edwards <s...@pubnub.com> wrote: > >> We are choosing to double our cluster from six to twelve. I ran the token >> generator. Based on what I read in the documentation, I expected to see the >> same first six tokens and six new tokens. Instead I see almost the same >> tokens but off by a few numbers. Is this expected? Should I change the >> similar tokens to the new ones? Am I doing it wrong? >> > > In your existing cluster, your first token is at > 28356863910078205288614550619314017621, which ends in an odd number. > > You cannot therefore choose a new token which exactly bisects its range, > because a node cannot own the token 28356863910078205288614550619314017621 > /2 = > 14178431955039102644307275309657008810.5 ... because tokens are integers. > > You will however notice that floor() of your current token divided by two > is your new token (14178431955039102644307275309657008810). > > I would personally keep my existing 6 tokens and do the simple math myself > of bisecting their ranges, not move my existing tokens around by one or two > tokens. > > =Rob > > > > > > >
