[
https://issues.apache.org/jira/browse/SENTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289882#comment-16289882
]
Na Li commented on SENTRY-1753:
-------------------------------
[~liamsargent] [~akolb] How about we suppress the specific exception. If we get
such exception before sentry gets full snapshot from HMS, i.e., sentry is ready
for HMS sync, we just log a info level message saying sentry is trying to
connect to HMS, but has not been successful. It is possible HMS service is not
fully started. Once sentry gets full snapshot from HMS, we stop suppressing
such exception.
Backing off the connection is not good idea since it is critical for sentry to
connect to HMS as soon as possible. Otherwise, Hive won't work properly. For
example, Hive cannot finish creating table while it waits for sentry to sync
with HMS and get the update of created table. After that, hive can let user to
configure permission for that new table.
> Make HMSFollower initial delay configurable
> -------------------------------------------
>
> Key: SENTRY-1753
> URL: https://issues.apache.org/jira/browse/SENTRY-1753
> Project: Sentry
> Issue Type: Task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Na Li
> Assignee: Liam Sargent
> Priority: Minor
>
> HMSFollower initial delay affects how fast it can get notification from Hive
> meta store. We are changing it from 60 seconds to 0 second. It may cause some
> issue. It is better to make this value configurable, so we can adjust it
> based on testing result.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
