What steps have you performed to add the new DC? Have you tried to follow
certain procedures like this?
Node can appear offline to other nodes for various reasons. It would help
greatly to know what steps you have taken in order to know why you're
Confidentiality warning: This message and any attachments are intended
only for the persons to whom this message is addressed, are confidential,
and may be privileged. If you are not the intended recipient, you are
hereby notified that any review, retransmission, conversion to hard copy,
copying, modification, circulation or other use of this message and any
attachments is strictly prohibited. If you receive this message in error,
please notify the sender immediately by return email, and delete this
message and any attachments from your system. Petrolink International
Limited its subsidiaries, holding companies and affiliates disclaims all
responsibility from and accepts no liability whatsoever for the
consequences of any unauthorized person acting, or refraining from acting,
on any information contained in this message. For security purposes, staff
training, to assist in resolving complaints and to improve our customer
service, email communications may be monitored and telephone calls may be
Gábor Auth <auth.ga...@gmail.com>
04/30/2018 03:40 PM
Please respond to
Re: Schema disagreement
On Mon, Apr 30, 2018 at 11:39 AM Gábor Auth <auth.ga...@gmail.com> wrote:
've just tried to add a new DC and new node to my cluster (3 DCs and 10
nodes) and the new node has a different schema version:
Is it normal? Node is marked down but doing a repair successfully?
WARN [MigrationStage:1] 2018-04-30 20:36:56,579 MigrationTask.java:67 -
Can't send schema pull request: node /x.x.216.121 is down.
INFO [AntiEntropyStage:1] 2018-04-30 20:36:56,611 Validator.java:281 -
[repair #323bf873-4cb6-11e8-bdd5-5feb84046dc9] Sending completed merkle
tree to /x.x.216.121 for keyspace.table
The `nodetool status` is looking good:
UN x.x.216.121 959.29 MiB 32 ?