Improve "liveness" probe implementation #552
Comments
emerkle826
added a commit
that referenced
this issue
Oct 22, 2024
burmanm
added a commit
that referenced
this issue
Oct 23, 2024
* In /liveness, verify that Cassandra is still running (if it was started) by checking the PID file exists and the PID is still running * If /start is called, check that pid is also running, not just present * Add issue #552 to Changelog --------- Co-authored-by: Erik Merkle <erik.merkle@datastax.com>
emerkle826
added a commit
that referenced
this issue
Oct 28, 2024
* [CHANGE] [#556](#556) Update Management API dependencies to address CVEs * [CHANGE] [#547](#547) Deprecate Cassandra 3.11 support * [FEATURE] [#551](#551) Add Cassandra 5.0.2 to the build matrix * [FEATURE] [#549](#549) Add DSE 6.9.3 to the build matrix * [ENHANCEMENT] [#552](#552) Improve "liveness" probe implementation * [BUGFIX] [#553](#553) Fix CassandraTaskExports metric filtering to make it work with 5.0.x Major compactions * [BUGFIX] [#560](#560) Fix LatencyMetrics bucketing on 4.1 and 5.0 as their reservoir stores the data in microseconds, not nano (unlike 3.11 and 4.0) * [BUGFIX] [#562](#562) Fix version detection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In K8s situations, bad config can cause issue with pod/container lifecycles and make it difficult to understand the root cause.
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: MAPI-73
The text was updated successfully, but these errors were encountered: