[ https://issues.apache.org/jira/browse/CASSANDRA-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Blake Eggleston updated CASSANDRA-19288: ---------------------------------------- Test and Documentation Plan: ci Status: Patch Available (was: Open) accord: [https://github.com/apache/cassandra-accord/pull/98] > Accord: Asynchronous reads may be unsafe > ---------------------------------------- > > Key: CASSANDRA-19288 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19288 > Project: Cassandra > Issue Type: Improvement > Components: Accord > Reporter: Benedict Elliott Smith > Assignee: Blake Eggleston > Priority: Normal > > In principle we should invalidate asynchronous reads before they complete if > the data they read may be invalid, but this anyway causes faults when we > permit them to occur in accord-core. We can and perhaps should simply ensure > the reads are issued against an sstable/memtable snapshot taken by the > command store, as this is lower cost and more robust. Otherwise we should > investigate what issue asynchronous reads cause. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org