[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866635/SENTRY-1649.040-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2650/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866635/SENTRY-1649.040-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2645/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866545/SENTRY-1649.039-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2641/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866427/SENTRY-1649.037-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2636/console

This message is automatically generated.

> 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
>
>
> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866333/SENTRY-1649.037-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 4 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationAdvanced
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2635/console

This message is automatically generated.

> 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.036-sentry-ha-redesign.patch, 
> SENTRY-1649.037-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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

The changes are
1. move starting HMSFollower from SentryService constructor to runServer() when 
starting SentryService. This allows getting notification after start()/stop() 
SentryService
2. create HMSFollower in runServer(). This allows HMSFollower to pick up 
different hive configuration after stop()/start() of SentryService.
3. HMSFollower.run() checks if the meta store URL is set in configuration. If 
not, return. This avoid creating local meta store.
4. Change HMSFollower initial start delay to 0 ms. Before, it was 60K ms (1 
minutes). This zero delay allows test verification happens after HMSFollower 
gets permission from hive. 
5. Close connections when HMSFollower.close() is called, which is called in 
SentryService.Stop().
6. Keep setting if we should get full snapshot in HMSFollower constructor. 
Otherwise, when the first full snapshot has nothing, a default AuthzObj is 
created in sentrystore. Since the latest notification ID is still 0, next run 
tries to get full snapshot again. When the second full snapshot has nothing, we 
have "SentryAlreadyExistsException: AuthzObj: default already exists". So I 
move the code for setting needHiveSnapshot back to 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, 
> SENTRY-1649.036-sentry-ha-redesign.patch, 
> SENTRY-1649.037-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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866318/SENTRY-1649.036-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 4 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationAdvanced
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2634/console

This message is automatically generated.

> 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.036-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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


[~lina.li] There are a lot of updates in this JIRA, can you summarize the 
result - what you are changing and what were the issues with tests that you had 
to get around or address.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866206/SENTRY-1649.035-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2629/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12866115/SENTRY-1649.034-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2627/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


Can you clarify why would one test start before another test completes? This 
shouldn't happen.



> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

I look at the log message for succeeded test and failed test. The reason of the 
test failure is
a) TestHDFSIntegrationBase.hiveServer2 is static (protected static 
InternalHiveServer hiveServer2;). 
b) When the test_1 is cleaning up and removing roles, test_2 has started and 
created new hiveServer2, and the roles created are removed by test_1. So test_2 
fails. 

Log messages:

1. For the succeeded test, the clean up messages, such as "Starting command: 
drop role col_role", from TestHDFSIntegrationBase.cleanAfterTest() only appear 
at the end of the log when the test ends.
2017-05-02 10:37:37,309 (HiveServer2-Handler-Pool: Thread-256) [INFO - 
org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:185)] 
Parsing command: drop role col_role
2017-05-02 10:37:37,349 (HiveServer2-Background-Pool: Thread-273) [INFO - 
org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1317)] Starting command: 
drop role col_role
2017-05-02 10:37:37,363 (pool-6-thread-3) [INFO - 
org.apache.sentry.provider.db.service.thrift.SentryPolicyStoreProcessor.drop_sentry_role(SentryPolicyStoreProcessor.java:441)]
 
{"serviceName":"Sentry-Service","userName":"hive","impersonator":"","ipAddress":"/127.0.0.1","operation":"DROP_ROLE","eventTime":"1493739457363","operationText":"DROP
 ROLE 
col_role","allowed":"true","databaseName":null,"tableName":null,"column":null,"resourcePath":null,"objectType":"ROLE"}


2. For failed test, the clean up messages, such as "Starting command: drop role 
col_role", appear at the beginning of the log and the end of log. Inidcating 
cleanAfterTest() was called at the beginning of the test and the end of the 
test. This removes the configuration setup for the test, and causes the test to 
fail.
2017-04-26 10:07:22,986 (HiveServer2-Background-Pool: Thread-1365) [INFO - 
org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1317)] Starting command: 
drop role col_role
2017-04-26 10:07:23,007 (pool-86-thread-3) [INFO - 
org.apache.sentry.provider.db.service.thrift.SentryPolicyStoreProcessor.drop_sentry_role(SentryPolicyStoreProcessor.java:441)]
 
{"serviceName":"Sentry-Service","userName":"hive","impersonator":"","ipAddress":"/127.0.0.1","operation":"DROP_ROLE","eventTime":"1493201243007","operationText":"DROP
 ROLE 
col_role","allowed":"true","databaseName":null,"tableName":null,"column":null,"resourcePath":null,"objectType":"ROLE"}

2017-04-26 10:06:00,674 (HiveServer2-Handler-Pool: Thread-255) [INFO - 
org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:185)] 
Parsing command: drop role 
col_role
2017-04-26 10:06:00,738 (HiveServer2-Background-Pool: Thread-446) [INFO - 
org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1317)] Starting command: 
drop role col_role
2017-04-26 10:06:00,762 (pool-6-thread-3) [INFO - 
org.apache.sentry.provider.db.service.thrift.SentryPolicyStoreProcessor.drop_sentry_role(SentryPolicyStoreProcessor.java:441)]
 
{"serviceName":"Sentry-Service","userName":"hive","impersonator":"","ipAddress":"/127.0.0.1","operation":"DROP_ROLE","eventTime":"1493201160762","operationText":"DROP
 ROLE 
col_role","allowed":"true","databaseName":null,"tableName":null,"column":null,"resourcePath":null,"objectType":"ROLE"}


> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865997/SENTRY-1649.033-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2626/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


I think SENTRY-1747 should address the test failures. My previous attempt here 
had a bug, need to retry with the right fix.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865897/SENTRY-1649.033-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2623/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


It looks like your changes exposed some deeper problem with the 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
>
>
> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865776/SENTRY-1649.032-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2613/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865619/SENTRY-1649.031-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2605/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865619/SENTRY-1649.031-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2601/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865261/SENTRY-1649.031-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2580/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

build 2573 and 2576 failed at 
"TestHDFSIntegrationEnd2End.testColumnPrivileges". It is not a stable test. And 
is reported in  (SENTRY-1723) Flaky test TestHDFSIntegrationEnd2End.

"Error Message

Error at verifying Path action : /user/hive/warehouse/db2.db/p1 ; 
expected: but was:
Stacktrace
java.lang.AssertionError: Error at verifying Path action : 
/user/hive/warehouse/db2.db/p1 ; expected: but was:
at 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End.testColumnPrivileges(TestHDFSIntegrationEnd2End.java:505)"

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865055/SENTRY-1649.030-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2576/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865055/SENTRY-1649.030-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2573/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

build 2567, 2569 and 2571 all fail at TestSentryWebServerWithSSL.setup(), and 
the exception is "Caused by: java.io.FileNotFoundException: 
/home/jenkins/jenkins-slave/workspace/PreCommit-SENTRY-Build%402/sentry-provider/sentry-provider-db/target/test-classes/keystore.jks
 (No such file or directory)" It happened for 3 different sentry issues with 
different patches. This issue was reported in SENTRY-1400 on 12/Jul/16 15:24

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

both sentry-1685 build 2567 and sentry-1649 build 2569 have the same failed 
test TestSentryWebServerWithSSL.setup, and both are caused by 
java.io.FileNotFoundException:

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865005/SENTRY-1649.030-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithSSL

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2569/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865005/SENTRY-1649.030-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2565/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864707/SENTRY-1649.026-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2558/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864523/SENTRY-1649.026-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 4 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2556/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864486/SENTRY-1649.026-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2555/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864430/SENTRY-1649.026-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2554/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864376/SENTRY-1649.024-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2549/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864347/SENTRY-1649.025-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithSSL

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2547/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864343/SENTRY-1649.024-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2546/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864322/SENTRY-1649.024-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2544/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864313/SENTRY-1649.024-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithSSL

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2543/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864020/SENTRY-1649.022-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2536/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

After moving starting HMSfollower to end of runServer(). the following test fail

Regression

org.apache.sentry.tests.e2e.metastore.TestDbNotificationListenerSentryDeserializer.testAlterPartition

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

Database N_db17 already exists
Stacktrace

org.apache.hadoop.hive.metastore.api.AlreadyExistsException: Database N_db17 
already exists
Standard Output

2017-04-19 04:54:17,617 (Thread-0) [INFO - 
org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.setupTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:284)]
 AbstractTestWithStaticConfiguration setupTestStaticConfiguration
2017-04-19 04:54:17,634 (Thread-0) [INFO - 
org.apache.sentry.tests.e2e.hive.AbstractTestWithStaticConfiguration.setupTestStaticConfiguration(AbstractTestWithStaticConfiguration.java:293)]
 BaseDir = /tmp/1492577657634-0
2017-04-19 04:54:18,329 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:446)] starting 
cluster: numNameNodes=1, numDataNodes=2
Formatting using clusterid: testClusterID
2017-04-19 04:54:18,948 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:716)]
 No KeyProvider found.
2017-04-19 04:54:18,948 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:726)]
 fsLock is fair:true
2017-04-19 04:54:18,999 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.DatanodeManager.(DatanodeManager.java:239)]
 dfs.block.invalidate.limit=1000
2017-04-19 04:54:19,000 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.DatanodeManager.(DatanodeManager.java:245)]
 dfs.namenode.datanode.registration.ip-hostname-check=true
2017-04-19 04:54:19,001 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.InvalidateBlocks.printBlockDeletionTime(InvalidateBlocks.java:71)]
 dfs.namenode.startup.delay.block.deletion.sec is set to 000:00:00:00.000
2017-04-19 04:54:19,003 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.InvalidateBlocks.printBlockDeletionTime(InvalidateBlocks.java:76)]
 The block deletion will start around 2017 Apr 19 04:54:19
2017-04-19 04:54:19,006 (Thread-0) [INFO - 
org.apache.hadoop.util.LightWeightGSet.computeCapacity(LightWeightGSet.java:354)]
 Computing capacity for map BlocksMap
2017-04-19 04:54:19,006 (Thread-0) [INFO - 
org.apache.hadoop.util.LightWeightGSet.computeCapacity(LightWeightGSet.java:355)]
 VM type   = 64-bit
2017-04-19 04:54:19,008 (Thread-0) [INFO - 
org.apache.hadoop.util.LightWeightGSet.computeCapacity(LightWeightGSet.java:356)]
 2.0% max memory 1.8 GB = 36.4 MB
2017-04-19 04:54:19,009 (Thread-0) [INFO - 
org.apache.hadoop.util.LightWeightGSet.computeCapacity(LightWeightGSet.java:361)]
 capacity  = 2^22 = 4194304 entries
2017-04-19 04:54:19,045 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.createBlockTokenSecretManager(BlockManager.java:358)]
 dfs.block.access.token.enable=false
2017-04-19 04:54:19,046 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:344)]
 defaultReplication = 2
2017-04-19 04:54:19,046 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:345)]
 maxReplication = 512
2017-04-19 04:54:19,048 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:346)]
 minReplication = 1
2017-04-19 04:54:19,049 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:347)]
 maxReplicationStreams  = 2
2017-04-19 04:54:19,049 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:348)]
 replicationRecheckInterval = 3000
2017-04-19 04:54:19,049 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:349)]
 encryptDataTransfer= false
2017-04-19 04:54:19,049 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.(BlockManager.java:350)]
 maxNumBlocksToLog  = 1000
2017-04-19 04:54:19,056 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:746)]
 fsOwner = jenkins (auth:SIMPLE)
2017-04-19 04:54:19,057 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:747)]
 supergroup  = supergroup
2017-04-19 04:54:19,057 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:748)]
 isPermissionEnabled = true
2017-04-19 04:54:19,057 (Thread-0) [INFO - 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.(FSNamesystem.java:759)]
 

[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863938/SENTRY-1649.021-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.metastore.TestDbNotificationListenerSentryDeserializer

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2535/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863731/SENTRY-1649.020-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2529/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863680/SENTRY-1649.019-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2527/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863499/SENTRY-1649.018-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2524/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863477/SENTRY-1649.017-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2522/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863476/SENTRY-1649.016-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2521/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863356/SENTRY-1649.015-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2513/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863351/SENTRY-1649.014-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2512/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863335/SENTRY-1649.013-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2510/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863335/SENTRY-1649.013-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2509/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863331/SENTRY-1649.012-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 4 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.thrift.TestSentryWebServerWithSSL
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2508/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863305/SENTRY-1649.010-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2505/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863308/SENTRY-1649.011-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2506/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863285/SENTRY-1649.009-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2504/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863285/SENTRY-1649.009-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.generic.service.persistent.TestPrivilegeOperatePersistence

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2503/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12863198/SENTRY-1649.008-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2502/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862973/SENTRY-1649.007-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2501/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862970/SENTRY-1649.006-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.dbprovider.TestDbSentryOnFailureHookLoading

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2500/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


Looking more at this it looks like it is possible to cancel execution using 
future's cancel method, but all this seems to be rather complicated - in this 
case shutting down the executor seems simpler. And you do need to shut it down 
on exit anyway.

> Initialize HMSFollower when sentry server actually starts
> -
>
> Key: SENTRY-1649
> URL: https://issues.apache.org/jira/browse/SENTRY-1649
> Project: Sentry
>  Issue Type: Sub-task
>  Components: Hdfs Plugin
>Affects Versions: sentry-ha-redesign
>Reporter: Hao Hao
>Assignee: Na Li
>Priority: Critical
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1649.001-sentry-ha-redesign.patch, 
> SENTRY-1649.002-sentry-ha-redesign.patch, 
> SENTRY-1649.003-sentry-ha-redesign.patch, 
> SENTRY-1649.004-sentry-ha-redesign.patch, 
> SENTRY-1649.005-sentry-ha-redesign.patch, 
> SENTRY-1649.006-sentry-ha-redesign.patch
>
>
> Now HMSFollower has been initialized at the constructor of SentryService. It 
> would be better to initialize it when the service starts, e.g runServer().



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


Why do you want to use future for de-scheduling? Are you sure that it does the 
right thing? What's wrong with the simple 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, 
> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862969/SENTRY-1649.005-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to 3 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2499/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862879/SENTRY-1649.004-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2496/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

My latest update does not destroy one instance. You can take a look at 
"https://reviews.apache.org/r/58221/diff/3#1"; 
sentry/service/thrift/SentryService.java. It is created in SentryService 
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.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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


Looking at the way HMSFollower is implemented I don't see why do you need to 
actually destroy one instance and create a new one when you want to start/stop 
it. The service is managed using the executor so the only thing you need to do 
is to stop or start *executing* the service.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862503/SENTRY-1649.003-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2490/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862351/SENTRY-1649.002-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2486/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on SENTRY-1649:
---

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12862160/SENTRY-1649.001-sentry-ha-redesign.patch
 against sentry-ha-redesign.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: 
https://builds.apache.org/job/PreCommit-SENTRY-Build/2485/console

This message is automatically generated.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


Thanks, this is accessible now.

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

Sorry, I forgot to publish it. Can you check if it is accessible now?

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on SENTRY-1649:


The review link isn't accessible:

{code}
You don't have access to this review request.

This review request is private. You must be a requested reviewer, either 
directly or on a requested group, and have permission to access the repository 
in order to view this review request.
{code}

> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

code review link https://reviews.apache.org/r/58221/


> 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] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts

[Na Li (JIRA)]

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

Na Li commented on SENTRY-1649:
---

We need to support multiple start/stop of sentry service. Therefore, start 
sentry service should be moved to what start() will execute. The reason e2e 
test fails is because it tries to start/stop sentry service multiple times. 
This change should fix the e2e 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
>
>
> 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)