[
https://issues.apache.org/jira/browse/CASSANDRA-21527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100071#comment-18100071
]
Stefan Miklosovic commented on CASSANDRA-21527:
-----------------------------------------------
Thanks, couple issues though:
1) CompactionManager.submitMaximal:1199 — getMaximalTasks(...) can return null
(from runWithCompactionsDisabled), then tasks.isEmpty() NPEs. Live path:
nodetool compact when an equal/higher-priority compaction is running.
2) ColumnFamilyStore.releaseRepairData force-branch (:1969) returns null,
propagates to ActiveRepairService:440 summary.toComposite() NPE. Live path:
nodetool repair_admin cleanup --force.
3) truncateBlocking finally { viewManager.build(); } can throw and mask the
TruncateException the whole patch exists to propagate (turns TRUNCATE_FAILED
into a generic UNKNOWN)
> truncateBlocking silently succeeds when runWithCompactionsDisabled returns
> null
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-21527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21527
> Project: Apache Cassandra
> Issue Type: Bug
> Reporter: Nivy Kani
> Assignee: Nivy Kani
> Priority: Normal
> Attachments: ci_summary-1.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar.gz
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, runWithCompactionsDisabled can’t tell the difference between a
> successful truncate vs a truncate that wasn’t successful due to being unable
> to stop compaction, because both return null. In either case, it logs
> “Truncate is complete” and returns success to the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
