[
https://issues.apache.org/jira/browse/ZOOKEEPER-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961781#comment-14961781
]
Arshad Mohammad commented on ZOOKEEPER-2295:
--------------------------------------------
The Error message was: nextRefresh: Sat Oct 17 11:13:18 IST 2015 is in the
past: exiting refresh thread. Check clock sync between this host and KDC -
(KDC's clock is likely ahead of this host). Manual intervention will be
required for this client to successfully authenticate. Exiting refresh thread.
> TGT refresh time logic is wrong
> -------------------------------
>
> Key: ZOOKEEPER-2295
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2295
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Arshad Mohammad
> Assignee: Arshad Mohammad
> Attachments: ZOOKEEPER-2295-01.patch
>
>
> When Kerberos is used as authentication mechanism some time TGT is getting
> expired because it is not refreshed timely.
> The scenario is as follow:
> suppose now=8 (the current milliseconds)
> next refresh time= 10
> TGT expire time= 9
> *Current behaviour:* Error is logged and TGT refresh thread exits.
> *Expected behaviour:* TGT should be refreshed immediately(now) instead of
> nextRefreshTime
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
