[
https://issues.apache.org/jira/browse/SENTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289724#comment-16289724
]
Alexander Kolbasov commented on SENTRY-1753:
--------------------------------------------
What is this simple solution? Delay connecting to HMS? Why would that be useful?
When Sentry starts HMS may be already running, starting up, not running at all
- no one knows or can guess. Suppose Sentry server crashed and restarted - this
means that HMS is already running and Sentry wants to connect to it right away
without any delay.
Delaying Sentry attempts to connect to HMS doesn't make much sense to me.
If you want to solve the excessive logging problem it is another story - it is
a reasonable request to suppress excessive logging from the same problem
happening every half a second.
> 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)
