[
https://issues.apache.org/jira/browse/ZOOKEEPER-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930141#comment-15930141
]
ASF GitHub Bot commented on ZOOKEEPER-2712:
-------------------------------------------
GitHub user rakeshadr opened a pull request:
https://github.com/apache/zookeeper/pull/200
ZOOKEEPER-2712: MiniKdc test case intermittently failing due to princ…
After long long analysis, I have observed concurrency issues at `ApacheDs
`(used for unit test) causing the trouble and failing minikdc test cases.
Introduced delay between the ZK server's startup to avoid simultaneous login
context init across servers. Also, modified few test code for better debugging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rakeshadr/zookeeper-1 ZK-2712
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/200.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #200
----
commit 3d1db97770a23ab8a9d9dd5700544518f865647a
Author: Rakesh Radhakrishnan <rake...@apache.org>
Date: 2017-03-17T15:25:56Z
ZOOKEEPER-2712: MiniKdc test case intermittently failing due to principal
not found in Kerberos database
----
> MiniKdc test case intermittently failing due to principal not found in
> Kerberos database
> ----------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 3.4.10
>
> Attachments:
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos
> database (6)
> {code}
> Will attach the detailed log to jira.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
