Roy Dahan
Roy Dahan
Seems like a similar/same issue happened in 2024.1.17, in this run: https://argus.scylladb.com/tests/scylla-cluster-tests/4ce66ccc-4f34-46b4-a6b4-2195ac5d608f ``` 2025-04-15 00:51:26.295 : (DatabaseLogEvent Severity.ERROR) period_type=one-time event_id=2cdb2735-62c5-4405-8d9f-1b6c71cc8b28 during_nemesis=GrowShrinkCluster: type=DATABASE_ERROR regex=(^ERROR|!\s*?ERR).*\[shard.*\] line_number=15472 node=longevity-parallel-topology-schema--db-node-4ce66ccc-13 2025-04-15T00:51:23.893+00:00 longevity-parallel-topology-schema--db-node-4ce66ccc-13 !ERR | scylla[6804]:...
> It doesn't look similar. In that case, I'll split it into a different issue. EDIT: https://github.com/scylladb/scylla-enterprise/issues/5372
Is this still relevant? Does scylla even support this command? I think lately we just removed it from dtest.
@Bouncheck this may be similar / same to the other issues you have in java-driver about driver get stuck after finishing. It may be easier to debug it with this...
Added to the current sprint as you already have the similar items planned for this sprint.
@dkropachev possibly we need to do the same thing @soyacz did in SCT for the "stuck" c-s.
Let's remove this test from gating until it's getting fixed. We shouldn't drag such issues for that long for flakey tests.
@fruch is taking care of it.
On one hand, I don't like it, but OTOH we can't continue wasting our time in investigations of the same issues... @fruch, if we merge it, add to the issue...
> > On one hand, I don't like it, but OTOH we can't continue wasting our time in investigations of the same issues... > > @fruch, if we merge it,...