[
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452989#comment-17452989
]
Paulo Motta edited comment on CASSANDRA-17180 at 12/3/21, 1:03 PM:
-------------------------------------------------------------------
And in the new config model this would probably fit well in a startup checks
section, something along these lines:
{code}
startup_checks:
check_data_dirs: true
check_gc_grace_seconds: true
check_correct_rack: true
{code}
was (Author: paulo):
And in the new config model this would probably fit well in a startup checks
section, something along these lines:
{nocode}
startup_checks:
check_data_dirs: true
check_gc_grace_seconds: true
check_correct_rack: true
{nocode}
> 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
