[
https://issues.apache.org/jira/browse/HBASE-23881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052541#comment-17052541
]
Josh Elser commented on HBASE-23881:
------------------------------------
{quote}I'm still digging, but I think it has to do with the semantics of
ConnectionImplementation in 2.x versus ConnectionOverAsyncConnection in master.
ConnectionImplementation would make a call to {{isMasterRunning}} when creating
the Master RPC stub. This ultimately triggers the above error, trying to parse
the response, erroring out, and retrying the RPC. That is, it's circumstantial
that we got an _unrelated to authentication error_ which caused branch 2.x to
execute the retry logic.
{quote}
Yup, I think this is it. If I take out the call to {{isMasterRunning(stub)}} in
{{ConnectionImplementation}}, we fall into the {{fail()}} in the test case
itself (just like in Master).
I'm satisfied at this point. Will take a look at the Netty RPC impl -- should
be straightforward to test/correct now that we know what's going on
(SaslClient.isComplete() returns true "sooner" than we expect it to for PLAIN
mechanism).
> TestShadeSaslAuthenticationProvider failures
> --------------------------------------------
>
> Key: HBASE-23881
> URL: https://issues.apache.org/jira/browse/HBASE-23881
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Bharath Vissapragada
> Assignee: Josh Elser
> Priority: Major
>
> TestShadeSaslAuthenticationProvider now fails deterministically with the
> following exception..
> {noformat}
> java.lang.Exception: Unexpected exception,
> expected<org.apache.hadoop.hbase.DoNotRetryIOException> but
> was<java.io.IOException>
> at
> org.apache.hadoop.hbase.security.provider.example.TestShadeSaslAuthenticationProvider.testNegativeAuthentication(TestShadeSaslAuthenticationProvider.java:233)
> {noformat}
> The test now fails a different place than before merging HBASE-18095 because
> the RPCs are also a part of connection setup. We might need to rewrite the
> test..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
