Israel Fruchter
Israel Fruchter
@bhalevy @xemul I think it might be related to change in https://github.com/scylladb/scylla-dtest/pull/3814 The specific test was doing only 100 requests in the background thread You changed to keep on going...
> Driver complains > ``` > E cassandra.OperationTimedOut: errors={'127.0.79.1:9042': 'Client request timeout. See Session.execute[_async](timeout)'}, last_host=127.0.79.1:9042 > ``` > > In node-1 logs I have > > ``` > 20:05:30,608 [shard...
happened again on Nov 14 https://70f106c98484448dbc4705050eb3f7e9.us-east-1.aws.found.io:9243/goto/98885b60-844f-11ee-bf28-5927cc3d3ce3 seems like we don't wait enough time in wait_other_notice, and the replacement might take more then 2min for now taking it out gating
@tchaikov one small question, is this issue observed, when running from within the toolchain image ?
> No, as the description of the issue puts, I hit this when testing on fedora39, not in the dbuild container. Can you check if Doing those steps: https://python-driver.docs.scylladb.com/stable/installation.html#libev-support And...
> > > No, as the description of the issue puts, I hit this when testing on fedora39, not in the dbuild container. > > > > > > Can...
> okay, i think the decision was made based on the assumption that asyncio worked. we proven it to work, and it pass the driver integration tests, but only when...
> cc @fruch @temichus see above the test is flaky by design, after several driver improvements it just changed how the flakiness shows. We need to either take it out...
@kbr-scylla regardless here a PR that disable the driver retries, and do it's own retrying https://github.com/scylladb/scylla-dtest/pull/3984
> ### Issue description > ``` > 01:53:37 < t:2024-02-16 23:53:32,087 f:health_checker.py l:60 c:sdcm.utils.health_checker p:WARNING > Gossip info is not available. Search for the warning above > 01:53:37 < t:2024-02-16...