[
https://issues.apache.org/jira/browse/HIVE-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386117#comment-15386117
]
Aihua Xu commented on HIVE-10574:
---------------------------------
I spent some time understanding the logic. Seems like we are only doing the
token validation when the client connects to the metastore. After the client
gets the token, it's free to talk to metastore, while the token could have
expired.
To fully solve the issue, similar to http request, we need to carry token for
each request to the metastore, the metastore needs to validate the token before
processing each request. If the token is expired, then the client should get
notified and try to get a new token. If the token is near-expired (e.g.,
half-way of the token life time), then we should renew the token to expend to a
full life time.
Hope it makes sense.
> Metastore to handle expired tokens inline
> -----------------------------------------
>
> Key: HIVE-10574
> URL: https://issues.apache.org/jira/browse/HIVE-10574
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Xuefu Zhang
> Assignee: Aihua Xu
>
> This is a followup for HIVE-9625.
> Metastore has a garbage collection thread that removes expired tokens.
> However that still leaves a window (1 hour by default) where clients could
> retrieve a token that's expired or about to expire. An option is for
> metastore handle expired tokens inline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
