[ https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461527#comment-17461527 ]
Josh McKenzie commented on CASSANDRA-17180: ------------------------------------------- bq. 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 Hygiene question: why are we changing the configuration paradigm for the {{FileSystemOwnershipCheck}} and for {{CheckGcGraceSecondsOnStartupOptions}} on a ticket unrelated to those two features? I'm good with us tidying up those two things but slipping them into this patch here just caught my eye as being somewhat suspicious. > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org