crate / crate-qa

CrateDB Quality Assurance
4 stars 1 forks source link

Set worker count for rolling upgrade tests #268

Closed mfussenegger closed 1 year ago

mfussenegger commented 1 year ago

The rolling upgrade tests are also flaky, sometimes getting stuck with a select count(*) from sys.shards where state = 'STARTED' on the 4.4.0 upgrade step.

This change is mostly to rule out the threading deadlock mentioned in https://github.com/crate/crate-qa/commit/cc3efd5ec3c24bc0fb0f7906dabc6f27462caaa1 as a reason. There are no blobs involved in the rolling upgrade, so this likely doesn't fix it.


If this doesn't work out we may have to wrap cursor.execute calls into a thread and apply a timeout + retry.