[
https://issues.apache.org/jira/browse/CASSANDRA-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912687#comment-17912687
]
Brandon Williams commented on CASSANDRA-20188:
----------------------------------------------
Thanks, Paul!
I have added a
[dtest|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-20188] that
exploits IGNORED_SCHEMA_CHECK_ENDPOINTS to cause an unsolvable schema
disagreement, and then measures the hint directory to know that hints were
delivered in this state.
||Branch||CI||
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-20188-4.0]|[repeat|https://app.circleci.com/pipelines/github/driftx/cassandra/1821/workflows/7325dbd5-978c-4179-882b-6f40439b2d74/jobs/111246]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-20188-4.1]|[repeat|https://app.circleci.com/pipelines/github/driftx/cassandra/1820/workflows/f576f435-dd64-4b00-b7fa-f95977358015/jobs/111250]|
|[5.0|https://github.com/driftx/cassandra/tree/CASSANDRA-20188-5.0]|[repeat|https://app.circleci.com/pipelines/github/driftx/cassandra/1822/workflows/b2f5f4cb-d004-4ae7-800a-ec1baa7e5667/jobs/111251],
[latest|https://app.circleci.com/pipelines/github/driftx/cassandra/1822/workflows/b2f5f4cb-d004-4ae7-800a-ec1baa7e5667/jobs/111252]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-20188-trunk]|[repeat|https://app.circleci.com/pipelines/github/driftx/cassandra/1823/workflows/fcb0d8ac-c9fb-47c0-8c59-adec133bdf81/jobs/111253],
[latest|https://app.circleci.com/pipelines/github/driftx/cassandra/1823/workflows/fcb0d8ac-c9fb-47c0-8c59-adec133bdf81/jobs/111254]|
> Allow hint delivery during schema mismatch
> ------------------------------------------
>
> Key: CASSANDRA-20188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20188
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Hints
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> In CASSANDRA-2083 we made hints require schema agreement to avoid a flood of
> errors in case the table the hints were destined for did not yet exist.
> This, however, has other undesirable effects, such as making keeping upgrades
> in a mixed mode over a longer period of time less tenable. We should still
> try to deliver hints and back off if the destination table doesn't exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
