[
https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058509#comment-15058509
]
Chris Nauroth commented on ZOOKEEPER-2344:
------------------------------------------
bq. Tell me which branch you'd like patches against and I see what I can do too
Hi [[email protected]]. In general, patches are flowing into trunk and
branch-3.5 right now. I expect any trunk patch is also applicable to
branch-3.5. Bug fixes can also flow down to the branch-3.4 maintenance line
depending on the circumstances. For small patches to improve logging and
debugging like you're suggesting, I expect they'd be great candidates for
inclusion in branch-3.4. You'll likely need to create a different patch file
for branch-3.4.
> Provide more diagnostics/stack traces on SASL Auth failure
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-2344
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2344
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client, server
> Affects Versions: 3.4.7, 3.5.1
> Reporter: Steve Loughran
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
>
> When Kerberos decides it doesn't want to work, the JRE libraries provide some
> terse and unhelpful error messages.
> The only way to debug the problem is (a) to have complete stack traces and
> (b) as much related information as possible.
> Zookeeper could do more here. Currently too much of the code loses stack
> traces; sometimes auth errors aren't reported back to the client (the
> connection is closed) +others
> Everyone who has tried to diagnose kerberos problems will appreciate
> improvements here
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
