[
https://issues.apache.org/jira/browse/CASSANDRA-21290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072523#comment-18072523
]
Stefan Miklosovic commented on CASSANDRA-21290:
-----------------------------------------------
trunk
https://app.circleci.com/pipelines/github/instaclustr/cassandra/6349/workflows/e2851e9e-9f35-4feb-a935-dc328df78cb0
5.0
https://app.circleci.com/pipelines/github/instaclustr/cassandra/6346/workflows/f1069147-f9e2-47a6-bce1-9197f861e828
not great not terrible, important that it this patch does not break anything.
Going to ship it.
> Implement atomic heartbeat file write
> -------------------------------------
>
> Key: CASSANDRA-21290
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21290
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: John Lu
> Assignee: John Lu
> Priority: Normal
> Fix For: 4.1.x, 5.0.x, 6.x
>
>
> It is possible for an empty heartbeat file to be written, potentially due to
> crash between file creation and the actual write. We can instead write to a
> temporary heartbeat file and then do an atomic move to rename it to the
> actual heartbeat file.
>
> Also fall back to the last modified time of the heartbeat file in case the
> file is not able to be parsed (it wont be able to be parsed if its empty)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
