[
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461820#comment-17461820
]
Stefan Miklosovic edited comment on CASSANDRA-17180 at 12/18/21, 9:44 AM:
--------------------------------------------------------------------------
[~jmckenzie] I admit that maybe I am over-reaching here in terms of changes but
that is just a natural conseqence of us wanting to have checks configurable. If
I have not changed it, we would have half baked solution and I would need to
return to messing with FileSystemOwnershipCheck in turn. I do not see any value
in splitting this configuration effort into two. Are you ok with this or do you
insist on reverting changes in FileSystemOwnershipCheck and pushing this
without that one covered?
BTW the configuration paradigm is not changed in this ticket. FS check is still
configurable via system properties as it was before. There is system properties
approach which takes precendence over yaml config and I want to get rid of the
original one in next major.
was (Author: smiklosovic):
[~jmckenzie] I admit that maybe I am over-reaching here in terms of changes but
that is just a natural conseqence of us wanting to have checks configurable. If
I have not changed it, we would have half baked solution and I would need to
return to messing with FileSystemOwnershipCheck in turn. I do not see any value
in splitting this configuration effort into two. Are you ok with this or do you
insist on reverting changes in FileSystemOwnershipCheck and pushing this
without that one covered?
BTW the configuration paradigm is not changed in this ticket. FS check is still
configurable via system properties as it was before.
> 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
