[ https://issues.apache.org/jira/browse/DRILL-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Wu updated DRILL-7035: -------------------------- Affects Version/s: 1.12.0 Description: [~debraj92] found that when under some circumstance the SaslAuthenticatorImpl's sasl_dispose() function will crash out at destruction. The incident seems to be random and only when certain authentication and encryption combinations are used during connection. After digging a little deeper, I found that when BOOST communication error occurs, the shutdownSocket (eventually triggering sasl_dispose()) could be called from various threads resulting in a race condition of freeing the handle. This can be reproduced with the querysubmitter. This is reproducible since 1.12.0+. [~debraj92] will be adding a patch to resolve this incident. was: [~debraj92] found that when under some circumstance the SaslAuthenticatorImpl's sasl_dispose() function will crash out at destruction. The incident seems to be random and only when certain authentication and encryption combinations are used during connection. After digging a little deeper, I found that when BOOST communication error occurs, the shutdownSocket (eventually triggering sasl_dispose()) could be called from various threads resulting in a race condition of freeing the handle. This can be reproduced with the querysubmitter. [~debraj92] will be adding a patch to resolve this incident. > Drill C++ Client crashes on multiple SaslAuthenticatorImpl Destruction due to > communication error > -------------------------------------------------------------------------------------------------- > > Key: DRILL-7035 > URL: https://issues.apache.org/jira/browse/DRILL-7035 > Project: Apache Drill > Issue Type: Bug > Components: Client - C++ > Affects Versions: 1.12.0 > Reporter: Rob Wu > Priority: Major > > [~debraj92] found that when under some circumstance the > SaslAuthenticatorImpl's sasl_dispose() function will crash out at > destruction. The incident seems to be random and only when certain > authentication and encryption combinations are used during connection. > After digging a little deeper, I found that when BOOST communication error > occurs, the shutdownSocket (eventually triggering sasl_dispose()) could be > called from various threads resulting in a race condition of freeing the > handle. This can be reproduced with the querysubmitter. This is reproducible > since 1.12.0+. > [~debraj92] will be adding a patch to resolve this incident. -- This message was sent by Atlassian JIRA (v7.6.3#76005)