[
https://issues.apache.org/jira/browse/CASSANDRA-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773285#comment-16773285
]
Jeff Jirsa commented on CASSANDRA-9384:
---------------------------------------
Think about this from the user side -
- Someone's going to bounce.
- They may or may not see the logs.
- If they had rounds=31, the password hashes arent going to match
- Newly bounced hosts will reject new connections, but the app will keep
working for a while.
- All the connections will stack up on the unbounced hosts until they're
overloaded
- Eventually the cluster will tip due to concentrating connections on a few
coordinators OR you'll eventually cause an outage due to removing all
coordinators with working auth.
That's not a great user story.
> Update jBCrypt dependency to version 0.4
> ----------------------------------------
>
> Key: CASSANDRA-9384
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9384
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Dinesh Joshi
> Priority: Major
> Fix For: 2.1.x, 2.2.x, 3.0.x, 3.11.x
>
>
> https://bugzilla.mindrot.org/show_bug.cgi?id=2097
> Although the bug tracker lists it as NEW/OPEN, the release notes for 0.4
> indicate that this is now fixed, so we should update.
> Thanks to [~Bereng] for identifying the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
