You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2026/10/17 13:33:00 UTC
[jira] [Created] (CASSANDRA-21767) Accord: first read of untouched key times out
Michael Semb Wever created CASSANDRA-21767:
----------------------------------------------
Summary: Accord: first read of untouched key times out
Key: CASSANDRA-21767
URL: https://issues.apache.org/jira/browse/CASSANDRA-21767
Project: Apache Cassandra
Issue Type: Bug
Components: Accord
Reporter: Michael Semb Wever
On a new cluster I have seen null dereferences of the value returned by {{SafeCommandStore.get(RoutingKey)}}, at two call sites:
* {{SafeCommandStore.updateManagedCommandsForKey:521}}, invoking {{SafeCommandsForKey.callback}}.
* {{Commands.setDurable:1384}}, invoking {{SafeCommandsForKey.setDurable}} through {{InformDurable}}.
{{AbstractSafeCommandStore.canExecute()}} used a non-null reference as proof that a key was ready. Incremental Cassandra tasks retain references for keys outside their current initialised batch. Those references pass the presence check but {{SafeCommandStore.get(key)}} returns {{null}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org