Github user hanm commented on the issue:
https://github.com/apache/zookeeper/pull/254
>> Will this results in any consistency issues later?
I guess the previous behavior was problematic and the fact
tunnelAuthInProgress always return false once a login failed (even after a new
connection retry attempt) is a bug that this JIRA trying to fix, right? If we
keep the old semantic then the bug will not be fixed because of the details
described in the JIRA - basically if we keep the old semantic and always return
false upon a failed login then the future SASL packet will be treated as normal
packet and got ignored - thus SASL login will never succeed..
>> so multiple threads are accessing the flag.
Yeah this looks like the case - so should we set the flag as volatile?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
