[
https://issues.apache.org/jira/browse/CASSANDRA-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536061#comment-17536061
]
Brandon Williams commented on CASSANDRA-10709:
----------------------------------------------
bq. shouldn't anymore see CASSANDRA-17416. Maybe we should loop it or do you
think it's totally unrelated
Ah, but 17416 was only closed two days ago - I haven't rebased so my patch is
against a week-old trunk. So I think the failure makes logical sense here, but
let's find out:
[branch|https://github.com/driftx/cassandra/tree/CASSANDRA-10709-trunk],
[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/475/workflows/edde972c-3c40-48bf-bff3-1f75b38918a8],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/475/workflows/564a94f1-36d0-476c-9495-b423af7206a6].
> Synchronize TOC and digest
> --------------------------
>
> Key: CASSANDRA-10709
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10709
> Project: Cassandra
> Issue Type: Bug
> Reporter: Stefania Alborghetti
> Assignee: Maciej Sokol
> Priority: Low
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-beta
>
>
> The TOC and DIGEST components are not synchronized at the moment (the file is
> not fsynch-ed to disk after it is written). This could cause inconsistencies
> in case of power failures. At the moment these component sstable files are
> only used by standalone tools but we should fix them nonetheless.
> Refer to the discussion on CASSANDRA-10534 for more details.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
