[jira] [Updated] (CASSANDRA-19872) Handle losing CMS status while committing a transformation

["Marcus Eriksson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-19872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-19872:
----------------------------------------
     Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998)
       Complexity: Normal
    Discovered By: Fuzz Test
    Fix Version/s: 5.x
        Reviewers: David Capwell
         Severity: Low
           Status: Open  (was: Triage Needed)

Found by [~dcapwell] in CASSANDRA-19847 - test is in that ticket

> Handle losing CMS status while committing a transformation
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-19872
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19872
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Normal
>             Fix For: 5.x
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a small window where we might try to use the wrong processor when committing a transformation while the CMS changes - in this case we should just retry the commit and we'll use the RemoteProcessor



--
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