Traffic stability during rolling upgrades

tnozicka commented 8 months ago

This is a tracker for our epic to make sure rolling restarts are graceful and no connection gets handled ungracefully.

Unfortunately, at this point we use services that publish unready endpoints and the traffic gets errors, or gets stuck in contract tables. There are also graceful termination fixes needed for handling ScyllaDB shutdown.

- [ ] https://github.com/scylladb/scylla-operator/pull/1614
- [ ] https://github.com/scylladb/scylladb/issues/15899
- [ ] https://github.com/scylladb/scylla-operator/issues/1077

scylla-operator-bot[bot] commented 2 weeks ago

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 30d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out

/lifecycle stale

tnozicka commented 2 weeks ago

/remove-lifecycle stale /triage accepted

scylladb / scylla-operator

Traffic stability during rolling upgrades #1577