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

David Capwell updated CASSANDRA-17754:
--------------------------------------
          Fix Version/s: 4.2
                             (was: 4.x)
          Since Version: 2.0.0
    Source Control Link: 
https://github.com/apache/cassandra/commit/db3a29428df5f4e17791ce8a4e075532abb36667
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> When bootstrap fails, CassandraRoleManager may attempt to do read queries 
> that fail with "Cannot read from a bootstrapping node", and increments 
> unavailables counters
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17754
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17754
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Bootstrap and Decommission, 
> Feature/Authorization
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 4.2
>
>
> If bootstrap fails we stay alive but avoid joining the ring.  
> CassandraRoleManager attempts to schedule its setup every 10 seconds, but 
> this will fail due to Bootstrap being pending; the side effect to this is 
> that readMetrics.unavailables gets incremented.
> We should defer attempting to setup only after we know its safe to perform 
> such as read



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

Reply via email to