[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Resolution: Fixed Status: Resolved (was: Patch Available) Transferring +1 from reviewboard. [~lina.li] Thank you for your contribution! > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-sentry-ha-redesign.patch, > SENTRY-1649.034-sentry-ha-redesign.patch, > SENTRY-1649.035-sentry-ha-redesign.patch, > SENTRY-1649.035-sentry-ha-redesign.patch, > SENTRY-1649.036-sentry-ha-redesign.patch, > SENTRY-1649.037-sentry-ha-redesign.patch, > SENTRY-1649.037-sentry-ha-redesign.patch, > SENTRY-1649.039-sentry-ha-redesign.patch, > SENTRY-1649.040-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.040-sentry-ha-redesign.patch v40. disable testViews due to sentry-1750 > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-sentry-ha-redesign.patch, > SENTRY-1649.034-sentry-ha-redesign.patch, > SENTRY-1649.035-sentry-ha-redesign.patch, > SENTRY-1649.035-sentry-ha-redesign.patch, > SENTRY-1649.036-sentry-ha-redesign.patch, > SENTRY-1649.037-sentry-ha-redesign.patch, > SENTRY-1649.037-sentry-ha-redesign.patch, > SENTRY-1649.039-sentry-ha-redesign.patch, > SENTRY-1649.040-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.039-sentry-ha-redesign.patch v39. fix unit test TestDbSentryOnFailureHookLoading. Increase wait time before verify in tests > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-sentry-ha-redesign.patch, > SENTRY-1649.034-sentry-ha-redesign.patch, > SENTRY-1649.035-sentry-ha-redesign.patch, > SENTRY-1649.035-sentry-ha-redesign.patch, > SENTRY-1649.036-sentry-ha-redesign.patch, > SENTRY-1649.037-sentry-ha-redesign.patch, > SENTRY-1649.037-sentry-ha-redesign.patch, > SENTRY-1649.039-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.035-sentry-ha-redesign.patch v35. start HMSFollower sooner and check needHiveSnapshot at constructor > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-sentry-ha-redesign.patch, > SENTRY-1649.034-sentry-ha-redesign.patch, > SENTRY-1649.035-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.034-sentry-ha-redesign.patch v34. use fix from 1734 and add more logging message in failed test > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-sentry-ha-redesign.patch, > SENTRY-1649.034-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Patch Available (was: Open) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Attachment: (was: SENTRY-1649.033-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Attachment: SENTRY-1649.033-sentry-ha-redesign.patch > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Open (was: Patch Available) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Patch Available (was: Open) Trying with disabled local metastore from HMSFollower > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Attachment: SENTRY-1649.033-sentry-ha-redesign.patch Avoid creating local metastore from HMSFollower > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-sentry-ha-redesign.patch, > SENTRY-1649.033-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Open (was: Patch Available) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.032-sentry-ha-redesign.patch v32. merge with latest updates > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.032-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.031-sentry-ha-redesign.patch v31. to trigger build. > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.031-sentry-ha-redesign.patch v31 again to trigger build > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-sentry-ha-redesign.patch, > SENTRY-1649.031-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.031-sentry-ha-redesign.patch v31. rebased on latest commits. identical to v30 > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.031-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.030-sentry-ha-redesign.patch v30 again. to trigger build > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.030-sentry-ha-redesign.patch v30. create HMSFollower in constructor to avoid unit test failures > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.021-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.028-sentry-ha-redesign.patch v28 again to trigger build > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.016-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.020-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.019-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.017-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.018-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.007-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.014-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.012-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.008-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.006-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.028-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.011-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.013-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.009-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.010-sentry-ha-redesign.patch) > 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.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.003-sentry-ha-redesign.patch) > 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.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.002-sentry-ha-redesign.patch) > 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.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: lina_test.patch) > 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.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.005-sentry-ha-redesign.patch) > 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.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > 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.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.028-sentry-ha-redesign.patch rebase for SENTRY-1691. v28 > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.027-sentry-ha-redesign.patch v27 again. not build result from previous attachment > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.026-sentry-ha-redesign.patch v26 4th times > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.026-sentry-ha-redesign.patch v26 the third time > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.026-sentry-ha-redesign.patch v26 again > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.026-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.026-sentry-ha-redesign.patch The same as v24, but rebased on the latest changes in sentry-ha-redesign branch. V26 > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.024-sentry-ha-redesign.patch v24 again > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.025-sentry-ha-redesign.patch create HMSFollower in constructor and startHMSFollower. See if that fixes the unit test failure. v25 > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.024-sentry-ha-redesign.patch > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.023-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.023-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.024-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: Sentry-1649 Patch24 Test fail.txt) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.024-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.001-sentry-ha-redesign.patch) > 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: lina_test.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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, Sentry-1649 Patch24 Test fail.txt > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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 Patch24 Test fail.txt > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, Sentry-1649 Patch24 Test fail.txt > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.024-sentry-ha-redesign.patch same as v23, but change version to v24 to trigger build > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.024-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.023-sentry-ha-redesign.patch attach v23 again to trigger build > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.023-sentry-ha-redesign.patch, > SENTRY-1649.023-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.023-sentry-ha-redesign.patch create HMSFollower in startHMSFollower and await termination after HMSFollower executor shutdownNow(). V23 > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.023-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.022-sentry-ha-redesign.patch move start HMSFollower at the start of runServer(). v22 > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.021-sentry-ha-redesign.patch move starting HMSfollower to end of runServer(). V21 > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.020-sentry-ha-redesign.patch remove extra code with patch v20 > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.019-sentry-ha-redesign.patch only start cleaner at runServer in patch version 19 > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.018-sentry-ha-redesign.patch some format change SENTRY-1649.018-sentry-ha-redesign.patch > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.017-sentry-ha-redesign.patch full change patch SENTRY-1649.017-sentry-ha-redesign.patch > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.016-sentry-ha-redesign.patch add patch SENTRY-1649.016-sentry-ha-redesign.patch. Remove formatting changes > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Patch Available (was: Open) > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Open (was: Patch Available) > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.014-sentry-ha-redesign.patch SENTRY-1649.014-sentry-ha-redesign.patch > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.013-sentry-ha-redesign.patch SENTRY-1649.013-sentry-ha-redesign.patch only call startSentryStoreCleaner() at constructor, and see if it fixes the test failure at building machine. > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.012-sentry-ha-redesign.patch test build SENTRY-1649.012-sentry-ha-redesign.patch > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.011-sentry-ha-redesign.patch SENTRY-1649.011-sentry-ha-redesign.patct create sentryStoreCleanService at very beginning to avoid timing issue. That may be the cause of the test failure. > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.010-sentry-ha-redesign.patch the patch file name is SENTRY-1649.010-sentry-ha-redesign.patch with minor change to get build machine why has "[DEBUG - org.apache.hadoop.util.Shell.checkHadoopHome(Shell.java:321)] Failed to detect a valid hadoop home directory java.io.IOException: HADOOP_HOME or hadoop.home.dir are not set." in org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence.testGrantPrivilegeExternalComponentInvalidConf > 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: lina_test.patch, > 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, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: lina_test.patch with minor change to get build machine why has "[DEBUG - org.apache.hadoop.util.Shell.checkHadoopHome(Shell.java:321)] Failed to detect a valid hadoop home directory java.io.IOException: HADOOP_HOME or hadoop.home.dir are not set." in org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence.testGrantPrivilegeExternalComponentInvalidConf > 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: lina_test.patch, > 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, > SENTRY-1649.009-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.009-sentry-ha-redesign.patch shutdown service executor at SentryService.stop() > 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, > SENTRY-1649.009-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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.007-sentry-ha-redesign.patch update for suggestions in code review by Sasha. > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.006-sentry-ha-redesign.patch version 006 is patch after rebase that includes all latest commites from remote sentry-ha-redesign > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.005-sentry-ha-redesign.patch 1. Implement HMSFollower.close(). Remove its start() and stop(). 2. Add SentryService.close(), executor service shutdown are moved there. in stop(), cancel the future of the tasks instead of shutting down executor services. 3. In SentryService$CommandImpl.run(), call SentryService.stop() and close() instead of just call serviceExecutor.shutdown(). > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.004-sentry-ha-redesign.patch fix the build error by including all changes in a single patch file. > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.003-sentry-ha-redesign.patch Create HMSFollower instance in SentryService constructor. start HMSFollower in SentryService.runServer and stop HMSFollower in SentryService.stop > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.002-sentry-ha-redesign.patch update based on code review. change code style and output exception > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Status: Patch Available (was: Open) move the scheduling of HMS follower to runServer(). > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ 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.001-sentry-ha-redesign.patch > 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 > > > 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)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mathew Crocker updated SENTRY-1649: --- Priority: Critical (was: Major) > 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 > > > 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)
