I suspect that cluster was created by recovering from a snapshot.
PS.
I asked a related question on this mailing list. Please check
subject: Removing initial_token parameter.
2018-03-08 20:02 GMT+07:00 Oleksandr Shulgin :
> On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin
> wrote:
>
>> Thank you
On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin wrote:
> Thank you for the answer, are you sure that it at least safe?
>
I would test in a lab first of course, but I don't see why it should be a
problem. I wonder more why did you have tokens listed explicitly on the
existing nodes if they are r
Thank you for the answer, are you sure that it at least safe?
As I understand I will have to specify auto_bootstrap=true too?
2018-03-08 18:16 GMT+07:00 Oleksandr Shulgin :
> On Thu, Mar 8, 2018 at 12:09 PM, Mikhail Tsaplin
> wrote:
>
>> Hi,
>>
>> I have a three node Cassandra cluster. Every nod
On Thu, Mar 8, 2018 at 12:09 PM, Mikhail Tsaplin wrote:
> Hi,
>
> I have a three node Cassandra cluster. Every node has initial_token
> configuration parameter holding 256 tokens (looks like randomly
> distributed). Now I have to add a fourth node. How could this be done?
>
I think the easiest a
Hi,
I have a three node Cassandra cluster. Every node has initial_token
configuration parameter holding 256 tokens (looks like randomly
distributed). Now I have to add a fourth node. How could this be done?
PS.
Part of 'nodetool ring' output:
192.168.1.123 rack1 Up Normal 2.84 T
