Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

init - Startup failed: std::runtime_error (bootstrap_with_repair: keyspace=system_distributed, range=(9183073555191895134, 9196226903124807343], no existing node in local dc) #6744

Closed
asias opened this issue Jul 2, 2020 · 4 comments
Closed

init - Startup failed: std::runtime_error (bootstrap_with_repair: keyspace=system_distributed, range=(9183073555191895134, 9196226903124807343], no existing node in local dc) #6744

asias opened this issue Jul 2, 2020 · 4 comments
Assignees
@asias
Labels
area/repair area/repair-based operations repare based node operations bug
Milestone
4.3

Comments

@asias
Copy link
Contributor

asias commented Jul 2, 2020

Consider a cluster with two nodes:

- n1 (dc1)
- n2 (dc2)

A third node is bootstrapped:

- n3 (dc2)

The n3 fails to bootstrap as follows:

[shard 0] init - Startup failed: std::runtime_error (bootstrap_with_repair: keyspace=system_distributed, range=(9183073555191895134, 9196226903124807343], no existing node in local dc)
asias added a commit to asias/scylla that referenced this issue Jul 2, 2020
@asias
repair: Relax node selection in bootstrap when nodes are less than RF
e76eb8b 
Consider a cluster with two nodes:

 - n1 (dc1)
 - n2 (dc2)

A third node is bootstrapped:

 - n3 (dc2)

The n3 fails to bootstrap as follows:

 [shard 0] init - Startup failed: std::runtime_error
 (bootstrap_with_repair: keyspace=system_distributed,
 range=(9183073555191895134, 9196226903124807343], no existing node in
 local dc)

The system_distributed keyspace is using SimpleStrategy with RF 3. For
the keyspace that does not use NetworkTopologyStrategy, we should not
require the source node to be in the same DC.

Fixes: scylladb#6744
Backports: 4.0 4.1, 4.2
@asias asias mentioned this issue Jul 2, 2020
Closed
@slivne
Copy link
Contributor

slivne commented Jul 2, 2020

@asias is this a regression

what happens with user tables ?

which versions are effected

@slivne slivne added this to the 4.3 milestone Jul 2, 2020
@slivne slivne added the high label Jul 2, 2020
@asias
Copy link
Contributor Author

asias commented Jul 2, 2020

@asias is this a regression

what happens with user tables ?

which versions are effected

Yes, it is a regression. It does matter it is a system or user table. Bootstrap a node with table using SimpleStrategy has this issue in case multiple DC are configured. Versions with repair based ops are affected.

@asias
Copy link
Contributor Author

asias commented Jul 2, 2020

Patch posted: #6745

avikivity pushed a commit that referenced this issue Jul 16, 2020
@asias @avikivity
repair: Relax node selection in bootstrap when nodes are less than RF
fb2ae9e 
Consider a cluster with two nodes:

 - n1 (dc1)
 - n2 (dc2)

A third node is bootstrapped:

 - n3 (dc2)

The n3 fails to bootstrap as follows:

 [shard 0] init - Startup failed: std::runtime_error
 (bootstrap_with_repair: keyspace=system_distributed,
 range=(9183073555191895134, 9196226903124807343], no existing node in
 local dc)

The system_distributed keyspace is using SimpleStrategy with RF 3. For
the keyspace that does not use NetworkTopologyStrategy, we should not
require the source node to be in the same DC.

Fixes: #6744
Backports: 4.0 4.1, 4.2
(cherry picked from commit 38d9643)
@avikivity
Copy link
Member

Backported to 4.2 (only version with repair based node ops enabled).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asias asias

Labels
area/repair area/repair-based operations repare based node operations bug
Projects
None yet
Milestone
4.3
Development

No branches or pull requests
4 participants
@asias @avikivity @slivne @scylladb-promoter