[
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460033#comment-17460033
]
Stefan Miklosovic edited comment on CASSANDRA-17180 at 12/15/21, 3:16 PM:
--------------------------------------------------------------------------
I have implemented configurable checks here:
[https://github.com/apache/cassandra/pull/1351/files]
While doing that, there is FileSystemOwnershipCheck which is reading some
system properties in order to configure itself. I have made it configurable too
but I left system properties resolution there too to be backward compatible
(system properties have precendece) so we will eventually get rid of that way
of configuring it. I have created respective properties in
CassandraRelevantProperties and aligned all tests.
Some checks are not trully checks, they are just setting something or logging.
Like jemalloc or inspecting jvm options or so. It is up to following discussion
if we make these "checks" unconfigurable (but they will be still executed).
was (Author: smiklosovic):
I have implemented configurable checks here:
[https://github.com/apache/cassandra/pull/1351/files]
While doing that, there is FileSystemOwnershipCheck which is reading some
system properties in order to configure itself. I have made it configurable too
but I left system properties resolution there too to be backward compatible
(system properties have precendece) so we will eventually get rid of that way
of configuring it. I have created respective properties in
CassandraRelevantProperties and aligned all tests.
> Implement heartbeat service to know last time Cassandra node was up
> -------------------------------------------------------------------
>
> Key: CASSANDRA-17180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17180
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Observability
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As already discussed on ML, it would be nice to have a service which would
> periodically write timestamp to a file signalling it is up / running.
> Then, on the startup, we would read this file and we would determine if there
> is some table which gc grace is behind this time and we would fail the start
> so we would prevent zombie data to be likely spread around a cluster.
> https://lists.apache.org/thread/w4w5t2hlcrvqhgdwww61hgg58qz13glw
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
