Julia Yakovlev
Julia Yakovlev
c-s load failed during cluster rolling restart - failed to get QUORUM, not enough replicas available
> > > > Reactor stalls (32ms) and kernel callstacks > > > > > > > > > @juliayakovlev - where's the kernel stack? > > > > >...
> While `longevity-tls-50gb-3d-master-db-node-9adcc62d-5` decommissioning (`decommission_with_repair`), when repair completed, `longevity-tls-50gb-3d-master-db-node-9adcc62d-7` got segmentation fault and coredump. > > ``` > 2024-05-14T04:33:13.489+00:00 longevity-tls-50gb-3d-master-db-node-9adcc62d-7 !INFO | scylla[19079]: Segmentation fault on shard 2. > 2024-05-14T04:33:13.489+00:00...
c-s load failed during cluster rolling restart - failed to get QUORUM, not enough replicas available
> run from last week (`5.5.0~dev-20240501.af5674211dd4`): [https://argus.scylladb.com/test/98050732-dfe3-464c-a66a-f235bad30829/runs?additionalRuns[]=16ad5b7e-ab08-4d63-bfb3-ca368a4433f5](https://argus.scylladb.com/test/98050732-dfe3-464c-a66a-f235bad30829/runs?additionalRuns%5B%5D=16ad5b7e-ab08-4d63-bfb3-ca368a4433f5) > > passed via this nemesis with success > > @juliayakovlev, let give it antheor run, to see if reproducible The issue was...
c-s load failed during cluster rolling restart - failed to get QUORUM, not enough replicas available
Reproducer with rolling restart cluster nemesis only. Issue was reproduced while first nemesis run.   ## Packages Scylla version: `5.5.0~dev-20240510.28791aa2c1d3` with build-id `893c2a68becf3d3bcbbf076980b1b831b9b76e29`...
c-s load failed during cluster rolling restart - failed to get QUORUM, not enough replicas available
Issue was not reproduced with Scylla version `5.4.6` https://argus.scylladb.com/test/a1c2befc-bd68-457a-ba19-913607256e6f/runs?additionalRuns[]=e0f3aa44-fb22-40a4-b406-91e16ada6c1b
c-s load failed during cluster rolling restart - failed to get QUORUM, not enough replicas available
> @juliayakovlev - anything relevant in the replica logs at the time of failure? I did not find nothing new
This error received while `drop keyspace`. "disrupt_add_remove_dc" nemesis 1. Create new keyspace: ``` < t:2024-01-13 07:54:19,129 f:common.py l:1748 c:utils p:DEBUG > Executing CQL 'CREATE KEYSPACE IF NOT EXISTS keyspace_new_dc WITH...
> @juliayakovlev steps you provided are a little bit confusing to me, is it possible for you to rewrite the steps-to-reproduce without referring to the test framework, so that I...
Reproduced with `5.5.0~dev-20240510` During `NoCorruptRepair` nemesis. Scenario: 1. create 10 keyspaces with one table 2. run c-s write load on every keyspaces 3. run repair 4. drop all 10 keyspaces...