[
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453028#comment-17453028
]
Stefan Miklosovic edited comment on CASSANDRA-17180 at 12/3/21, 2:07 PM:
-------------------------------------------------------------------------
Thanks Paulo for the review. Interesting point about the optional startup
checks and new configuration model related to that. While I do not object your
idea, I am not sure how to time your proposal because it is not related to what
I want to do . In other words, I would dedicate a new ticket which would cover
the changes you mentioned AND THEN we would return to this ticket and implement
it so all necessary configuration changes are already in place. More to it, I
can imagine that this particular startup check will accept more fields in its
configuration - if it is enabled and what is the path to the heartbeat file to
read plus as you mentioned, what are the tables this check should skip. I
imagine something like this:
{code:java}
startup_checks:
data_dirs:
enabled: true
gc_grace_seconds:
enabled: true
correct_rack:
enabled: true
heartbeat:
enabled: true
file: .cassandra-heartbeat
ignored_tables:
- ks1.tb1
- ks2.tb2
- ks3 // would ignore whole keyspace
{code}
How does this sound to you?
was (Author: smiklosovic):
Thanks Paulo for the review. Interesting point about the optional startup
checks and new configuration model related to that. While I do not object your
idea, I am not sure how to time your proposal because it is not related to what
I want to do . In other words, I would dedicate a new ticket which would cover
the changes you mentioned AND THEN we would return to this ticket and implement
it so all necessary configuration changes are already in place. More to it, I
can imagine that this particular startup check will accept more fields in its
configuration - if it is enabled and what is the path to the heartbeat file to
read plus as you mentioned, what are the tables this check should skip. I
imagine something like this:
startup_checks:
data_dirs:
enabled: true
gc_grace_seconds:
enabled: true
correct_rack:
enabled: true
heartbeat:
enabled: true
file: .cassandra-heartbeat
ignored_tables:
- ks1.tb1
- ks2.tb2
- ks3 // would ignore whole keyspace
How does this sound to you?
> 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]
