[
https://issues.apache.org/jira/browse/HIVE-15090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615471#comment-15615471
]
Peter Vary commented on HIVE-15090:
-----------------------------------
I have tested with the following configuration:
{code}
<property>
<!-- So the tokens are stored in database -->
<name>hive.cluster.delegation.token.store.class</name>
<value>org.apache.hadoop.hive.thrift.DBTokenStore</value>
</property>
<property>
<!-- So the removal happens often -->
<name>hive.cluster.delegation.token.gc-interval</name>
<value>10</value>
</property>
{code}
Started the Metastore, and after a while I have stopped the database. When the
database was turned off the metastore logged the {{ExpiredTokenRemover thread
received unexpected exception}} message, after the database restarted the
messages are stopped, and everything become normal. In the debugger I have
verified the thread is running.
> Temporary DB failure can stop ExpiredTokenRemover thread
> --------------------------------------------------------
>
> Key: HIVE-15090
> URL: https://issues.apache.org/jira/browse/HIVE-15090
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 2.2.0
> Reporter: Peter Vary
> Assignee: Peter Vary
> Attachments: HIVE-15090.patch
>
>
> In HIVE-13090 we decided that we should not close the metastore if there is
> an unexpected exception during the expired token removal process, but that
> fix leaves a running metastore without ExpiredTokenRemover thread.
> To fix this I will move the catch inside the running loop, and hope the
> thread could recover from the exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
