[ 
https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Na Li updated SENTRY-1649:
--------------------------
    Attachment: SENTRY-1649.008-sentry-ha-redesign.patch

change the order of scheduling SentryStoreCleaner, trying to fix build error 
below:
----------------
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading.org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading

Failing for the past 1 build (Since Failed#2500 )
Took 4.3 sec.
Error Message

got: <[null]>, expected: each not null
Stacktrace

org.junit.internal.AssumptionViolatedException: got: <[null]>, expected: each 
not null
        at 
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading.setup(TestDbSentryOnFailureHookLoading.java:48)

> 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, 
> SENTRY-1649.007-sentry-ha-redesign.patch, 
> SENTRY-1649.008-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)

Reply via email to