zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database
Date Sat, 18 Mar 2017 22:06:41 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931408#comment-15931408
] 

Michael Han commented on ZOOKEEPER-2712:
----------------------------------------

[~rakeshr] Good job on hunting down the culprit of the race! 

I am curious what exactly cause the races though - from the description it was not very clear
to me. Do you mind to elaborate a little bit with regards to what code in test case that uses
what function in the dependency library and what the race condition is?

Regarding find bug warnings - I tried find bugs (3.0.1) locally and I also get 97 warnings.
I suspect we did not get such warnings either because we did not run find bugs at all for
branch-3.4, or find bug version updates. I think we should fix the warnings before releasing
of 3.4.10, not sure if you agree with this or not. Regardless of this, I think fixing findbug
warning is out scope of this particular JIRA and we could use another JIRA to track it (same
for the javadoc warnings).

> 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
>            Priority: Critical
>             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 learner@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)

Mime
View raw message