You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Liam Sargent (JIRA)" <ji...@apache.org> on 2017/12/13 17:03:00 UTC

[jira] [Commented] (SENTRY-1753) Make HMSFollower initial delay configurable

    [ https://issues.apache.org/jira/browse/SENTRY-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289531#comment-16289531 ] 

Liam Sargent commented on SENTRY-1753:
--------------------------------------

[~LinaAtAustin] - does this presence of this code in org.apache.sentry.service.thrift.ServiceConstants ->

{{// InitialDelay and period time for HMSFollower thread.
    public static final String SENTRY_HMSFOLLOWER_INIT_DELAY_MILLS = "sentry.hmsfollower.init.delay.mills";
    public static final long SENTRY_HMSFOLLOWER_INIT_DELAY_MILLS_DEFAULT = 0;}}

Mean this is already completed?

> 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
>            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)