[
https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965384#comment-15965384
]
Alexander Kolbasov commented on SENTRY-1649:
--------------------------------------------
Looking more at this it looks like it is possible to cancel execution using
future's cancel method, but all this seems to be rather complicated - in this
case shutting down the executor seems simpler. And you do need to shut it down
on exit anyway.
> Initialize HMSFollower when sentry server actually starts
> ---------------------------------------------------------
>
> Key: SENTRY-1649
> URL: https://issues.apache.org/jira/browse/SENTRY-1649
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
> Affects Versions: sentry-ha-redesign
> Reporter: Hao Hao
> Assignee: Na Li
> Priority: Critical
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1649.001-sentry-ha-redesign.patch,
> SENTRY-1649.002-sentry-ha-redesign.patch,
> SENTRY-1649.003-sentry-ha-redesign.patch,
> SENTRY-1649.004-sentry-ha-redesign.patch,
> SENTRY-1649.005-sentry-ha-redesign.patch,
> SENTRY-1649.006-sentry-ha-redesign.patch
>
>
> Now HMSFollower has been initialized at the constructor of SentryService. It
> would be better to initialize it when the service starts, e.g runServer().
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
