Stuck topology request after increasing replication factor

ScyllaDB
, , ,
1

Installation details
#ScyllaDB version: 6.2
#Cluster size: 30 nodes x 1 dc
#OS: Ubuntu 24.04

Hey everybody,

I encounter some issues with a stuck topology request after increasing the replication factor. The query which caused it was:ALTER KEYSPACE uniprottry WITH replication = { ‘class’ : ‘NetworkTopologyStrategy’, ‘cubimedrubdc’ : 3}

I put the results of

cqlsh:uniprottry> select * from system.topology_requests ;
cqlsh:uniprottry> select * from system.topology where global_topology_request_id = 75105bf2-cb73-11f0-d73b-a33c60dc186d allow filtering;

here: Stuck topology request after increasing RF · GitHub

It look suspicously like: , but I have no ghost nodes.Nodetool is reporting all nodes are up normal (UN) on every node.

Increasing the repliction factor to 2, a few days earlier worked flawlessly.

Is there something I can do to get rid of these stuck topology requests?

Best,Dirk

2

Sorry, the link was missing

https://forum.scylladb.com/t/stuck-topology-requests/4856
3

As time is rather limited and everything I tried to solve this issue was unsuccessfull, I moved the data to a new cluster.

1 Like