[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1593: Attachment: SENTRY-1593.010-sentry-ha-redesign.patch > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > SENTRY-1593.010-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1593: Attachment: (was: SENTRY-1593.010-sentry-ha-redesign.patch) > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.030-sentry-ha-redesign.patch v30 again. to trigger build > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984085#comment-15984085 ] kalyan kumar kalvagadda commented on SENTRY-1593: - This is passed locally. > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > SENTRY-1593.010-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (SENTRY-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984085#comment-15984085 ] kalyan kumar kalvagadda edited comment on SENTRY-1593 at 4/26/17 2:46 AM: -- This test passed locally. was (Author: kkalyan): This is passed locally. > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > SENTRY-1593.010-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984082#comment-15984082 ] Na Li commented on SENTRY-1685: --- the failure in build 2567 seems to be issue at build machine. not related to code change 2017-04-26 00:39:07,363 (SentryService-0) [ERROR - org.apache.sentry.service.thrift.SentryService.call(SentryService.java:234)] Error starting server java.security.PrivilegedActionException: 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) > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li > Labels: merge > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1685.001-sentry-ha-redesign.patch, > SENTRY-1685.002-sentry-ha-redesign.patch > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1593) Implement client failover for Generic and NN clients
[
https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984045#comment-15984045
]
Hadoop QA commented on SENTRY-1593:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865036/SENTRY-1593.010-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/2571/console
This message is automatically generated.
> Implement client failover for Generic and NN clients
>
>
> Key: SENTRY-1593
> URL: https://issues.apache.org/jira/browse/SENTRY-1593
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: kalyan kumar kalvagadda
>Priority: Blocker
> Labels: HA
> Fix For: sentry-ha-redesign
>
> Attachments: old_service_client_class_diagram.png,
> SENTRY-1593.001-sentry-ha-redesign.patch,
> SENTRY-1593.002-sentry-ha-redesign.patch,
> SENTRY-1593.003-sentry-ha-redesign.patch,
> SENTRY-1593.004-sentry-ha-redesign.patch,
> SENTRY-1593.005-sentry-ha-redesign.patch,
> SENTRY-1593.006-sentry-ha-redesign.patch,
> SENTRY-1593.007-sentry-ha-redesign.patch,
> SENTRY-1593.009-sentry-ha-redesign.patch,
> SENTRY-1593.010-sentry-ha-redesign.patch,
> service_client_class_diagram_latest_v1.png, service_client_class_diagram.png
>
>
> We need to have client failover logic for Generic service clients and Name
> Node clients. Currently only db policy clients have it implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1687) FullUpdateInitializer can be more efficient
[
https://issues.apache.org/jira/browse/SENTRY-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984040#comment-15984040
]
Hadoop QA commented on SENTRY-1687:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865043/SENTRY-1687.001-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.TestSentryWebServerWithKerberos
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2570/console
This message is automatically generated.
> FullUpdateInitializer can be more efficient
> ---
>
> Key: SENTRY-1687
> URL: https://issues.apache.org/jira/browse/SENTRY-1687
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1687.001-sentry-ha-redesign.patch
>
>
> The FullUpdateInitializer follows the {{MetastoreCacheInitializer}}. It reads
> a bunch of information from HMS and uses Thrift structures to pass around,
> but in the end it just constructs {{Map}}. It uses
> concurrent fetches from HMS, but synchronizes a lot on common data structures
> to update them.
> I think that we can refactor all this code to make it faster and consume less
> memory. The idea is the following:
> Use background threads to collect Thrift results from HMS calls (database,
> table and partition data). Then we can use a single thread to construct the
> resulting update and return it without using intermediate Thrift methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[
https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984037#comment-15984037
]
Hadoop QA commented on SENTRY-1685:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864999/SENTRY-1685.002-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/2568/console
This message is automatically generated.
> Port SENTRY-1489 to sentry-ha-redesign branch
> -
>
> Key: SENTRY-1685
> URL: https://issues.apache.org/jira/browse/SENTRY-1685
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Na Li
> Labels: merge
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1685.001-sentry-ha-redesign.patch,
> SENTRY-1685.002-sentry-ha-redesign.patch
>
>
> We need to port SENTRY-1489 to sentry-ha-redesign branch
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1708) Extend the current test classes to handle multiple sentry servers
[
https://issues.apache.org/jira/browse/SENTRY-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984002#comment-15984002
]
Hadoop QA commented on SENTRY-1708:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12865026/SENTRY-1708.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/2566/console
This message is automatically generated.
> Extend the current test classes to handle multiple sentry servers
> -
>
> Key: SENTRY-1708
> URL: https://issues.apache.org/jira/browse/SENTRY-1708
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: kalyan kumar kalvagadda
>Assignee: kalyan kumar kalvagadda
> Labels: test
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1708.001-sentry-ha-redesign.patch,
> SENTRY-1708.001-sentry-ha-redesign.patch
>
>
> we need to extend the base classes like SentryServiceIntegrationBase which is
> used my a lot tests to work with multiple sentry servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SENTRY-1724) Remove old PoolClientInvocationHandler
Alexander Kolbasov created SENTRY-1724: -- Summary: Remove old PoolClientInvocationHandler Key: SENTRY-1724 URL: https://issues.apache.org/jira/browse/SENTRY-1724 Project: Sentry Issue Type: Sub-task Components: Sentry Affects Versions: sentry-ha-redesign Reporter: Alexander Kolbasov Old PoolClientInvocationHandler is no longer supported and should be removed, -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1687) FullUpdateInitializer can be more efficient
[
https://issues.apache.org/jira/browse/SENTRY-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1687:
---
Attachment: SENTRY-1687.001-sentry-ha-redesign.patch
> FullUpdateInitializer can be more efficient
> ---
>
> Key: SENTRY-1687
> URL: https://issues.apache.org/jira/browse/SENTRY-1687
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1687.001-sentry-ha-redesign.patch
>
>
> The FullUpdateInitializer follows the {{MetastoreCacheInitializer}}. It reads
> a bunch of information from HMS and uses Thrift structures to pass around,
> but in the end it just constructs {{Map}}. It uses
> concurrent fetches from HMS, but synchronizes a lot on common data structures
> to update them.
> I think that we can refactor all this code to make it faster and consume less
> memory. The idea is the following:
> Use background threads to collect Thrift results from HMS calls (database,
> table and partition data). Then we can use a single thread to construct the
> resulting update and return it without using intermediate Thrift methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[
https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Updated] (SENTRY-1687) FullUpdateInitializer can be more efficient
[
https://issues.apache.org/jira/browse/SENTRY-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1687:
---
Status: Open (was: Patch Available)
> FullUpdateInitializer can be more efficient
> ---
>
> Key: SENTRY-1687
> URL: https://issues.apache.org/jira/browse/SENTRY-1687
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
>
> The FullUpdateInitializer follows the {{MetastoreCacheInitializer}}. It reads
> a bunch of information from HMS and uses Thrift structures to pass around,
> but in the end it just constructs {{Map}}. It uses
> concurrent fetches from HMS, but synchronizes a lot on common data structures
> to update them.
> I think that we can refactor all this code to make it faster and consume less
> memory. The idea is the following:
> Use background threads to collect Thrift results from HMS calls (database,
> table and partition data). Then we can use a single thread to construct the
> resulting update and return it without using intermediate Thrift methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1687) FullUpdateInitializer can be more efficient
[
https://issues.apache.org/jira/browse/SENTRY-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1687:
---
Attachment: (was: SENTRY-1687.001-sentry-ha-redesign.patch)
> FullUpdateInitializer can be more efficient
> ---
>
> Key: SENTRY-1687
> URL: https://issues.apache.org/jira/browse/SENTRY-1687
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
>
> The FullUpdateInitializer follows the {{MetastoreCacheInitializer}}. It reads
> a bunch of information from HMS and uses Thrift structures to pass around,
> but in the end it just constructs {{Map}}. It uses
> concurrent fetches from HMS, but synchronizes a lot on common data structures
> to update them.
> I think that we can refactor all this code to make it faster and consume less
> memory. The idea is the following:
> Use background threads to collect Thrift results from HMS calls (database,
> table and partition data). Then we can use a single thread to construct the
> resulting update and return it without using intermediate Thrift methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SENTRY-1723) Flaky test TestHDFSIntegrationEnd2End
Alexander Kolbasov created SENTRY-1723:
--
Summary: Flaky test TestHDFSIntegrationEnd2End
Key: SENTRY-1723
URL: https://issues.apache.org/jira/browse/SENTRY-1723
Project: Sentry
Issue Type: Sub-task
Components: Sentry
Reporter: Alexander Kolbasov
When I run the {{TestHDFSIntegrationEnd2End}} test from sentry-ha-redesign
branch, I get
{code}
---
T E S T S
---
Running org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End
Tests run: 6, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 142.788 sec <<<
FAILURE! - in org.apa
che.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End
testColumnPrivileges(org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End)
Time elapsed: 15.0
14 sec <<< FAILURE!
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(TestHDFSI
ntegrationEnd2End.java:505)
Results :
Flaked tests:
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationEnd2End.testColumnPrivileges(org.apache.sentry.te
sts.e2e.hdfs.TestHDFSIntegrationEnd2End)
Run 1:
TestHDFSIntegrationEnd2End.testColumnPrivileges:505->TestHDFSIntegrationBase.verifyOnAllSubDirs:186->TestHDFSIntegrationBase.verifyOnAllSubDirs:205->TestHDFSIntegrationBase.verifyOnAllSubDirs:209->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:234->TestHDFSIntegrationBase.verifyOnAllSubDirsHelper:224
Error at verifying Path action : /user/hive/warehouse/db2.db/p1 ;
expected: but was:
Run 2: PASS
Tests run: 5, Failures: 0, Errors: 0, Skipped: 2, Flakes: 1
{code}
I run the test with
{code}
mvn clean -pl sentry-tests/sentry-tests-hive -am -DfailIfNoTests=false
-Dtest=TestHDFSIntegrationEnd2End test
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[
https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[
https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983913#comment-15983913
]
Hadoop QA commented on SENTRY-1685:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864999/SENTRY-1685.002-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/2567/console
This message is automatically generated.
> Port SENTRY-1489 to sentry-ha-redesign branch
> -
>
> Key: SENTRY-1685
> URL: https://issues.apache.org/jira/browse/SENTRY-1685
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Na Li
> Labels: merge
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1685.001-sentry-ha-redesign.patch,
> SENTRY-1685.002-sentry-ha-redesign.patch
>
>
> We need to port SENTRY-1489 to sentry-ha-redesign branch
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1593: Attachment: SENTRY-1593.010-sentry-ha-redesign.patch > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > SENTRY-1593.010-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1593: Attachment: (was: SENTRY-1593.010-sentry-ha-redesign.patch) > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > SENTRY-1593.010-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1593) Implement client failover for Generic and NN clients
[ https://issues.apache.org/jira/browse/SENTRY-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1593: Attachment: SENTRY-1593.010-sentry-ha-redesign.patch > Implement client failover for Generic and NN clients > > > Key: SENTRY-1593 > URL: https://issues.apache.org/jira/browse/SENTRY-1593 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Blocker > Labels: HA > Fix For: sentry-ha-redesign > > Attachments: old_service_client_class_diagram.png, > SENTRY-1593.001-sentry-ha-redesign.patch, > SENTRY-1593.002-sentry-ha-redesign.patch, > SENTRY-1593.003-sentry-ha-redesign.patch, > SENTRY-1593.004-sentry-ha-redesign.patch, > SENTRY-1593.005-sentry-ha-redesign.patch, > SENTRY-1593.006-sentry-ha-redesign.patch, > SENTRY-1593.007-sentry-ha-redesign.patch, > SENTRY-1593.009-sentry-ha-redesign.patch, > SENTRY-1593.010-sentry-ha-redesign.patch, > service_client_class_diagram_latest_v1.png, service_client_class_diagram.png > > > We need to have client failover logic for Generic service clients and Name > Node clients. Currently only db policy clients have it implemented. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1720) Re-enable or remove TestHDFSIntegrationWithHA
[ https://issues.apache.org/jira/browse/SENTRY-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1720: --- Description: The TestHDFSIntegrationWithHA test is disabled now. We need to either fix it or remove if it is no longer applicable. The TestHDFSIntegration test is disabled as well. was:The TestHDFSIntegrationWithHA test is disabled now. We need to either fix it or remove if it is no longer applicable. > Re-enable or remove TestHDFSIntegrationWithHA > -- > > Key: SENTRY-1720 > URL: https://issues.apache.org/jira/browse/SENTRY-1720 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov > Labels: test > Fix For: sentry-ha-redesign > > > The TestHDFSIntegrationWithHA test is disabled now. We need to either fix it > or remove if it is no longer applicable. > The TestHDFSIntegration test is disabled as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1708) Extend the current test classes to handle multiple sentry servers
[ https://issues.apache.org/jira/browse/SENTRY-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1708: Attachment: SENTRY-1708.001-sentry-ha-redesign.patch > Extend the current test classes to handle multiple sentry servers > - > > Key: SENTRY-1708 > URL: https://issues.apache.org/jira/browse/SENTRY-1708 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: test > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1708.001-sentry-ha-redesign.patch, > SENTRY-1708.001-sentry-ha-redesign.patch > > > we need to extend the base classes like SentryServiceIntegrationBase which is > used my a lot tests to work with multiple sentry servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.030-sentry-ha-redesign.patch v30. create HMSFollower in constructor to avoid unit test failures > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch, > SENTRY-1649.029-sentry-ha-redesign.patch, > SENTRY-1649.030-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1722) Create HMSFollower when SentryService.Start() is called
[ https://issues.apache.org/jira/browse/SENTRY-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1722: -- Issue Type: Sub-task (was: Task) Parent: SENTRY-872 > Create HMSFollower when SentryService.Start() is called > --- > > Key: SENTRY-1722 > URL: https://issues.apache.org/jira/browse/SENTRY-1722 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Na Li >Assignee: Na Li > Labels: easyfix > Original Estimate: 4h > Remaining Estimate: 4h > > Right now, when creating HMSFollower when SentryService.Start() is called, > several unit tests fail. So we have to create it in SentryService > constructor. Once they are fixed, creating HMSFollower when > SentryService.Start() is called -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SENTRY-1722) Create HMSFollower when SentryService.Start() is called
Na Li created SENTRY-1722: - Summary: Create HMSFollower when SentryService.Start() is called Key: SENTRY-1722 URL: https://issues.apache.org/jira/browse/SENTRY-1722 Project: Sentry Issue Type: Task Components: Sentry Affects Versions: sentry-ha-redesign Reporter: Na Li Assignee: Na Li Right now, when creating HMSFollower when SentryService.Start() is called, several unit tests fail. So we have to create it in SentryService constructor. Once they are fixed, creating HMSFollower when SentryService.Start() is called -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1721) Unit test failures in TestSentryStore
[ https://issues.apache.org/jira/browse/SENTRY-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1721: -- Issue Type: Sub-task (was: Bug) Parent: SENTRY-872 > Unit test failures in TestSentryStore > - > > Key: SENTRY-1721 > URL: https://issues.apache.org/jira/browse/SENTRY-1721 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Na Li >Assignee: Na Li > Labels: test > Original Estimate: 96h > Remaining Estimate: 96h > > We encounter multiple incidents of unit test failures. They are mainly > TestSentryStore.testPrivilegesWithPermUpdate and > TestPrivilegeOperatePersistence.testGrantPrivilegeExternalComponentInvalidConf > These tests fail more often when HMSFollower is created after > SentryService.Start() is called. And less frequent when HMSFollower is > created in SentryService constructor. Need investigation on whether this is > just a bug in test cases or reflect issues in synchronization between Sentry > HMS metastore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SENTRY-1721) Unit test failures in TestSentryStore
Na Li created SENTRY-1721: - Summary: Unit test failures in TestSentryStore Key: SENTRY-1721 URL: https://issues.apache.org/jira/browse/SENTRY-1721 Project: Sentry Issue Type: Bug Components: Sentry Affects Versions: sentry-ha-redesign Reporter: Na Li Assignee: Na Li We encounter multiple incidents of unit test failures. They are mainly TestSentryStore.testPrivilegesWithPermUpdate and TestPrivilegeOperatePersistence.testGrantPrivilegeExternalComponentInvalidConf These tests fail more often when HMSFollower is created after SentryService.Start() is called. And less frequent when HMSFollower is created in SentryService constructor. Need investigation on whether this is just a bug in test cases or reflect issues in synchronization between Sentry HMS metastore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983528#comment-15983528 ] Na Li commented on SENTRY-1685: --- I compared the differences using https://www.diffchecker.com/diff. And the changes are the same as sentry-1489 SENTRY-1489.2.patch > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li > Labels: merge > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1685.001-sentry-ha-redesign.patch, > SENTRY-1685.002-sentry-ha-redesign.patch > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1685: -- Status: Patch Available (was: Open) > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li > Labels: merge > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1685.001-sentry-ha-redesign.patch, > SENTRY-1685.002-sentry-ha-redesign.patch > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1685: -- Attachment: SENTRY-1685.002-sentry-ha-redesign.patch v2, remove the extra space in "AbstractTestWithStaticConfiguration extends RulesForE2ETest " > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li > Labels: merge > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1685.001-sentry-ha-redesign.patch, > SENTRY-1685.002-sentry-ha-redesign.patch > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SENTRY-1720) Re-enable or remove TestHDFSIntegrationWithHA
Alexander Kolbasov created SENTRY-1720: -- Summary: Re-enable or remove TestHDFSIntegrationWithHA Key: SENTRY-1720 URL: https://issues.apache.org/jira/browse/SENTRY-1720 Project: Sentry Issue Type: Sub-task Components: Sentry Affects Versions: sentry-ha-redesign Reporter: Alexander Kolbasov The TestHDFSIntegrationWithHA test is disabled now. We need to either fix it or remove if it is no longer applicable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1685: -- Attachment: SENTRY-1685.001-sentry-ha-redesign.patch v1. port changes > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li > Labels: merge > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1685.001-sentry-ha-redesign.patch > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1708) Extend the current test classes to handle multiple sentry servers
[ https://issues.apache.org/jira/browse/SENTRY-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1708: Status: Patch Available (was: In Progress) > Extend the current test classes to handle multiple sentry servers > - > > Key: SENTRY-1708 > URL: https://issues.apache.org/jira/browse/SENTRY-1708 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: test > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1708.001-sentry-ha-redesign.patch > > > we need to extend the base classes like SentryServiceIntegrationBase which is > used my a lot tests to work with multiple sentry servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1708) Extend the current test classes to handle multiple sentry servers
[ https://issues.apache.org/jira/browse/SENTRY-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1708: Attachment: SENTRY-1708.001-sentry-ha-redesign.patch > Extend the current test classes to handle multiple sentry servers > - > > Key: SENTRY-1708 > URL: https://issues.apache.org/jira/browse/SENTRY-1708 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: kalyan kumar kalvagadda >Assignee: kalyan kumar kalvagadda > Labels: test > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1708.001-sentry-ha-redesign.patch > > > we need to extend the base classes like SentryServiceIntegrationBase which is > used my a lot tests to work with multiple sentry servers. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.021-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.028-sentry-ha-redesign.patch v28 again to trigger build > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.016-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.020-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.019-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.017-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.018-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.007-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.014-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.012-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.008-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.006-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.028-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.011-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.013-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.009-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.010-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.003-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.002-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: lina_test.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.005-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: lina_test.patch, > SENTRY-1649.002-sentry-ha-redesign.patch, > SENTRY-1649.003-sentry-ha-redesign.patch, > SENTRY-1649.004-sentry-ha-redesign.patch, > SENTRY-1649.005-sentry-ha-redesign.patch, > SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: lina_test.patch, > SENTRY-1649.002-sentry-ha-redesign.patch, > SENTRY-1649.003-sentry-ha-redesign.patch, > SENTRY-1649.004-sentry-ha-redesign.patch, > SENTRY-1649.005-sentry-ha-redesign.patch, > SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1649) Initialize HMSFollower when sentry server actually starts
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: (was: SENTRY-1649.026-sentry-ha-redesign.patch) > Initialize HMSFollower when sentry server actually starts > - > > Key: SENTRY-1649 > URL: https://issues.apache.org/jira/browse/SENTRY-1649 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Hao Hao >Assignee: Na Li >Priority: Critical > Fix For: sentry-ha-redesign > > Attachments: lina_test.patch, > SENTRY-1649.002-sentry-ha-redesign.patch, > SENTRY-1649.003-sentry-ha-redesign.patch, > SENTRY-1649.004-sentry-ha-redesign.patch, > SENTRY-1649.005-sentry-ha-redesign.patch, > SENTRY-1649.006-sentry-ha-redesign.patch, > SENTRY-1649.007-sentry-ha-redesign.patch, > SENTRY-1649.008-sentry-ha-redesign.patch, > SENTRY-1649.009-sentry-ha-redesign.patch, > SENTRY-1649.010-sentry-ha-redesign.patch, > SENTRY-1649.011-sentry-ha-redesign.patch, > SENTRY-1649.012-sentry-ha-redesign.patch, > SENTRY-1649.013-sentry-ha-redesign.patch, > SENTRY-1649.014-sentry-ha-redesign.patch, > SENTRY-1649.015-sentry-ha-redesign.patch, > SENTRY-1649.016-sentry-ha-redesign.patch, > SENTRY-1649.017-sentry-ha-redesign.patch, > SENTRY-1649.018-sentry-ha-redesign.patch, > SENTRY-1649.019-sentry-ha-redesign.patch, > SENTRY-1649.020-sentry-ha-redesign.patch, > SENTRY-1649.021-sentry-ha-redesign.patch, > SENTRY-1649.022-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.024-sentry-ha-redesign.patch, > SENTRY-1649.025-sentry-ha-redesign.patch, > SENTRY-1649.026-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.027-sentry-ha-redesign.patch, > SENTRY-1649.028-sentry-ha-redesign.patch > > > Now HMSFollower has been initialized at the constructor of SentryService. It > would be better to initialize it when the service starts, e.g runServer(). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1687) FullUpdateInitializer can be more efficient
[
https://issues.apache.org/jira/browse/SENTRY-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982745#comment-15982745
]
Hadoop QA commented on SENTRY-1687:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12864894/SENTRY-1687.001-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/2561/console
This message is automatically generated.
> FullUpdateInitializer can be more efficient
> ---
>
> Key: SENTRY-1687
> URL: https://issues.apache.org/jira/browse/SENTRY-1687
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1687.001-sentry-ha-redesign.patch
>
>
> The FullUpdateInitializer follows the {{MetastoreCacheInitializer}}. It reads
> a bunch of information from HMS and uses Thrift structures to pass around,
> but in the end it just constructs {{Map}}. It uses
> concurrent fetches from HMS, but synchronizes a lot on common data structures
> to update them.
> I think that we can refactor all this code to make it faster and consume less
> memory. The idea is the following:
> Use background threads to collect Thrift results from HMS calls (database,
> table and partition data). Then we can use a single thread to construct the
> resulting update and return it without using intermediate Thrift methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1488) Create scripts that DBA can use to collect scale and usage stats
[
https://issues.apache.org/jira/browse/SENTRY-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982741#comment-15982741
]
Hadoop QA commented on SENTRY-1488:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12831653/SENTRY-1488.0.patch
against master.
{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/2560/console
This message is automatically generated.
> Create scripts that DBA can use to collect scale and usage stats
>
>
> Key: SENTRY-1488
> URL: https://issues.apache.org/jira/browse/SENTRY-1488
> Project: Sentry
> Issue Type: New Feature
> Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1488.0.patch, stats-1.png, stats-2.png
>
>
> We could create a script/tool subfolder so that can add side tools into it.
> For example, we could simply create a script that gives us a row count of
> every table in the Sentry database, plus the same thing for every table in
> the Hive Metastore database. That will give us info like: total number of
> tables, total number of roles, total permissions, etc.
> To start with:
> {code}
> #Roles
> #Permissions
> #Groups
> #Permissions per Role: avg, medium and max
> #Roles per Permission: avg, medium and max
> #Groups per role: avg, medium and max
> #Roles per group: avg, medium and max
> #Databases
> #Tables
> #Views
> #Partitions
> #Tables per Database: avg, medium and max
> #Views per Database: avg, medium and max
> #Partitions per Table: avg, medium and max
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1540) SentryStore.isMultiActionsSupported() is always true
[
https://issues.apache.org/jira/browse/SENTRY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982684#comment-15982684
]
Hadoop QA commented on SENTRY-1540:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12846408/SENTRY-1540.v2.patch
against master.
{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/2562/console
This message is automatically generated.
> SentryStore.isMultiActionsSupported() is always true
>
>
> Key: SENTRY-1540
> URL: https://issues.apache.org/jira/browse/SENTRY-1540
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Alexander Kolbasov
>Assignee: Vamsee Yarlagadda
>Priority: Minor
> Labels: bite-sized
> Attachments: SENTRY-1540.v1.patch, SENTRY-1540.v2.patch
>
>
> The SentryStore.isMultiActionsSupported() function:
> {code}
> // Currently INSERT/SELECT/ALL are supported for Table and DB level
> privileges
> private boolean isMultiActionsSupported(TSentryPrivilege tPrivilege) {
> return tPrivilege.getDbName() != null;
> }
> {code}
> It is called in two places - in drop_privileges():
> {code}
> TSentryPrivilege tPrivilege = toSentryPrivilege(tAuthorizable);
> try {
> if (isMultiActionsSupported(tPrivilege)) {
> ...
> {code}
> The toSentryPrivilege() function:
> {code}
> private TSentryPrivilege toSentryPrivilege(TSentryAuthorizable
> tAuthorizable)
> throws SentryInvalidInputException {
> TSentryPrivilege tSentryPrivilege = new TSentryPrivilege();
> tSentryPrivilege.setDbName(fromNULLCol(tAuthorizable.getDb()));
> tSentryPrivilege.setServerName(fromNULLCol(tAuthorizable.getServer()));
> tSentryPrivilege.setTableName(fromNULLCol(tAuthorizable.getTable()));
> tSentryPrivilege.setColumnName(fromNULLCol(tAuthorizable.getColumn()));
> tSentryPrivilege.setURI(fromNULLCol(tAuthorizable.getUri()));
> ...
> {code}
> So all fields are initialized to an emoty string which means that
> isMultiActionsSupported is always true.
> The same is true for the second usage in renamePrivilege().
> So currently the function is meaningless. So it should be either removed or
> changed to verify that dbName is non-empty and not "__NULL__".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1547) It is possible to create a privilege with all empty fields
[
https://issues.apache.org/jira/browse/SENTRY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982670#comment-15982670
]
Hadoop QA commented on SENTRY-1547:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12843302/SENTRY-1547.002.patch
against master.
{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/2564/console
This message is automatically generated.
> It is possible to create a privilege with all empty fields
> --
>
> Key: SENTRY-1547
> URL: https://issues.apache.org/jira/browse/SENTRY-1547
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Alexander Kolbasov
>Assignee: kalyan kumar kalvagadda
>Priority: Minor
> Labels: bite-sized
> Attachments: SENTRY-1547.001.patch, SENTRY-1547.002.patch
>
>
> It is possible (at least by sending Thrift message) to create privilege with
> everything set to __NULL__ which is a pretty useless privilege. We should
> check that at least some fields are set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SENTRY-1502) Multiple tests in TestSentryStore are not testing useful things
[
https://issues.apache.org/jira/browse/SENTRY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982664#comment-15982664
]
Hadoop QA commented on SENTRY-1502:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12842223/SENTRY-1502.001.patch
against master.
{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/2563/console
This message is automatically generated.
> Multiple tests in TestSentryStore are not testing useful things
> ---
>
> Key: SENTRY-1502
> URL: https://issues.apache.org/jira/browse/SENTRY-1502
> Project: Sentry
> Issue Type: Test
> Components: Sentry
>Affects Versions: 1.7.0, sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Ruiming Zhou
> Labels: patch
> Fix For: 1.8.0
>
> Attachments: SENTRY-1502.001.patch
>
>
> I noticed that multiple unit tests in TestSentryStore are not testing useful
> things. For example:
> {code}
> @Test
> public void testCreateDropRole() throws Exception {
> String roleName = "test-drop-role";
> long seqId = sentryStore.createSentryRole(roleName).getSequenceId();
> assertEquals(seqId + 1,
> sentryStore.dropSentryRole(roleName).getSequenceId());
> }
> {code}
> So this code only tests that there are no exceptions thrown. The assert is
> bogus - it tests that there was a single transaction in between which is a
> wrong test in the first place - number of transactions isn't a functionality.
> The test doesn't verify whether the role was actually created and whether it
> was correctly dropped. And it is similar for other tests as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1574) SentryMetastorePostEventListenerBase class is not used by anything
[ https://issues.apache.org/jira/browse/SENTRY-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1574: --- Priority: Minor (was: Major) > SentryMetastorePostEventListenerBase class is not used by anything > -- > > Key: SENTRY-1574 > URL: https://issues.apache.org/jira/browse/SENTRY-1574 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Priority: Minor > Labels: bite-sized, newbie > > The SentryMetastorePostEventListenerBase class isn't used by anyone - time to > remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1574) SentryMetastorePostEventListenerBase class is not used by anything
[ https://issues.apache.org/jira/browse/SENTRY-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1574: --- Affects Version/s: (was: 1.8.0) > SentryMetastorePostEventListenerBase class is not used by anything > -- > > Key: SENTRY-1574 > URL: https://issues.apache.org/jira/browse/SENTRY-1574 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov > Labels: bite-sized, newbie > > The SentryMetastorePostEventListenerBase class isn't used by anyone - time to > remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1574) SentryMetastorePostEventListenerBase class is not used by anything
[ https://issues.apache.org/jira/browse/SENTRY-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1574: --- Issue Type: Sub-task (was: Improvement) Parent: SENTRY-872 > SentryMetastorePostEventListenerBase class is not used by anything > -- > > Key: SENTRY-1574 > URL: https://issues.apache.org/jira/browse/SENTRY-1574 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov > Labels: bite-sized, newbie > > The SentryMetastorePostEventListenerBase class isn't used by anyone - time to > remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1547) It is possible to create a privilege with all empty fields
[ https://issues.apache.org/jira/browse/SENTRY-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1547: --- Affects Version/s: (was: sentry-ha-redesign) > It is possible to create a privilege with all empty fields > -- > > Key: SENTRY-1547 > URL: https://issues.apache.org/jira/browse/SENTRY-1547 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Alexander Kolbasov >Assignee: kalyan kumar kalvagadda >Priority: Minor > Labels: bite-sized > Attachments: SENTRY-1547.001.patch, SENTRY-1547.002.patch > > > It is possible (at least by sending Thrift message) to create privilege with > everything set to __NULL__ which is a pretty useless privilege. We should > check that at least some fields are set. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1545) Deleted users and groups remain in the DB forever
[ https://issues.apache.org/jira/browse/SENTRY-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1545: --- Affects Version/s: (was: sentry-ha-redesign) > Deleted users and groups remain in the DB forever > - > > Key: SENTRY-1545 > URL: https://issues.apache.org/jira/browse/SENTRY-1545 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Alexander Kolbasov > > When a user or a group is removed from a role, the user or group is never > removed from the SENTRY_USER or SENTRY_GROUP table. Only the map table is > updated. This means that as users and groups are added and removed, these > table grow and may, eventually, become quite big. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1530) Sentry should use to io.dropwizard.metrics
[ https://issues.apache.org/jira/browse/SENTRY-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1530: --- Affects Version/s: (was: sentry-ha-redesign) > Sentry should use to io.dropwizard.metrics > -- > > Key: SENTRY-1530 > URL: https://issues.apache.org/jira/browse/SENTRY-1530 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Alexander Kolbasov >Priority: Minor > Attachments: SENTRY-1530.001.patch, SENTRY-1530.002.patch > > > The com.codahale.metrics is now io.dropwizard.metrics with current version > being 3.1.0. > We should consider moving Sentry to this version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1540) SentryStore.isMultiActionsSupported() is always true
[
https://issues.apache.org/jira/browse/SENTRY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1540:
---
Affects Version/s: (was: sentry-ha-redesign)
> SentryStore.isMultiActionsSupported() is always true
>
>
> Key: SENTRY-1540
> URL: https://issues.apache.org/jira/browse/SENTRY-1540
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Alexander Kolbasov
>Assignee: Vamsee Yarlagadda
>Priority: Minor
> Labels: bite-sized
> Attachments: SENTRY-1540.v1.patch, SENTRY-1540.v2.patch
>
>
> The SentryStore.isMultiActionsSupported() function:
> {code}
> // Currently INSERT/SELECT/ALL are supported for Table and DB level
> privileges
> private boolean isMultiActionsSupported(TSentryPrivilege tPrivilege) {
> return tPrivilege.getDbName() != null;
> }
> {code}
> It is called in two places - in drop_privileges():
> {code}
> TSentryPrivilege tPrivilege = toSentryPrivilege(tAuthorizable);
> try {
> if (isMultiActionsSupported(tPrivilege)) {
> ...
> {code}
> The toSentryPrivilege() function:
> {code}
> private TSentryPrivilege toSentryPrivilege(TSentryAuthorizable
> tAuthorizable)
> throws SentryInvalidInputException {
> TSentryPrivilege tSentryPrivilege = new TSentryPrivilege();
> tSentryPrivilege.setDbName(fromNULLCol(tAuthorizable.getDb()));
> tSentryPrivilege.setServerName(fromNULLCol(tAuthorizable.getServer()));
> tSentryPrivilege.setTableName(fromNULLCol(tAuthorizable.getTable()));
> tSentryPrivilege.setColumnName(fromNULLCol(tAuthorizable.getColumn()));
> tSentryPrivilege.setURI(fromNULLCol(tAuthorizable.getUri()));
> ...
> {code}
> So all fields are initialized to an emoty string which means that
> isMultiActionsSupported is always true.
> The same is true for the second usage in renamePrivilege().
> So currently the function is meaningless. So it should be either removed or
> changed to verify that dbName is non-empty and not "__NULL__".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1543) dropOrRenamePrivilegeForAllRoles() has confusing code
[
https://issues.apache.org/jira/browse/SENTRY-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1543:
---
Affects Version/s: (was: sentry-ha-redesign)
> dropOrRenamePrivilegeForAllRoles() has confusing code
> -
>
> Key: SENTRY-1543
> URL: https://issues.apache.org/jira/browse/SENTRY-1543
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Alexander Kolbasov
>Priority: Minor
> Labels: bite-sized, newbie
>
> {code}
> private void dropOrRenamePrivilegeForAllRoles(PersistenceManager pm,
> TSentryPrivilege tPrivilege,
> TSentryPrivilege newTPrivilege) throws SentryNoSuchObjectException,
> SentryInvalidInputException {
> HashSet roleSet = Sets.newHashSet();
> List mPrivileges = getMSentryPrivileges(tPrivilege, pm);
> if (mPrivileges != null && !mPrivileges.isEmpty()) {
> for (MSentryPrivilege mPrivilege : mPrivileges) {
> roleSet.addAll(ImmutableSet.copyOf(mPrivilege.getRoles()));
> }
> }
> MSentryPrivilege parent = getMSentryPrivilege(tPrivilege, pm);
> ...
> }
> {code}
> Note that first we do getMSentryPrivileges(tPrivilege) and then
> getMSentryPrivilege(tPrivilege). In the first case the list of multiple
> entries is returned, in the second only a single element is returned.
> The two calls construct query a bit differently - the getMSentryPrivilege()
> unconditionally adds filters for all components.
> So the intent here is rather confusing and it would be good to clarify in the
> comments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1494) Evaluate using a JSON notification log message as a Map rather than using a Deserializer with Java message object.
[ https://issues.apache.org/jira/browse/SENTRY-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1494: --- Affects Version/s: (was: sentry-ha-redesign) > Evaluate using a JSON notification log message as a Map rather than using a > Deserializer with Java message object. > -- > > Key: SENTRY-1494 > URL: https://issues.apache.org/jira/browse/SENTRY-1494 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Reporter: Sravya Tirukkovalur >Priority: Minor > Labels: improvement > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1502) Multiple tests in TestSentryStore are not testing useful things
[
https://issues.apache.org/jira/browse/SENTRY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982483#comment-15982483
]
Alexander Kolbasov commented on SENTRY-1502:
[~skya...@yahoo.com] Are you still working on this? There were no updates since
Dec 2016.
> Multiple tests in TestSentryStore are not testing useful things
> ---
>
> Key: SENTRY-1502
> URL: https://issues.apache.org/jira/browse/SENTRY-1502
> Project: Sentry
> Issue Type: Test
> Components: Sentry
>Affects Versions: 1.7.0, sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Ruiming Zhou
> Labels: patch
> Fix For: 1.8.0
>
> Attachments: SENTRY-1502.001.patch
>
>
> I noticed that multiple unit tests in TestSentryStore are not testing useful
> things. For example:
> {code}
> @Test
> public void testCreateDropRole() throws Exception {
> String roleName = "test-drop-role";
> long seqId = sentryStore.createSentryRole(roleName).getSequenceId();
> assertEquals(seqId + 1,
> sentryStore.dropSentryRole(roleName).getSequenceId());
> }
> {code}
> So this code only tests that there are no exceptions thrown. The assert is
> bogus - it tests that there was a single transaction in between which is a
> wrong test in the first place - number of transactions isn't a functionality.
> The test doesn't verify whether the role was actually created and whether it
> was correctly dropped. And it is similar for other tests as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1484) Automate generation of schema files
[ https://issues.apache.org/jira/browse/SENTRY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1484: --- Affects Version/s: (was: sentry-ha-redesign) > Automate generation of schema files > --- > > Key: SENTRY-1484 > URL: https://issues.apache.org/jira/browse/SENTRY-1484 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Alexander Kolbasov >Priority: Minor > > The schema files for various DB engines are maintained manually. We should > think of some automated or semi-automated ways of creating this. Ideally we'd > like these auto-generated by Datanucleus and dumped for us. An alternative is > to use some macro engine to describe schemas and having some tool to > automatically generate correct SQL syntax for various DB engines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1484) Automate generation of schema files
[ https://issues.apache.org/jira/browse/SENTRY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1484: --- Affects Version/s: (was: 1.7.0) 1.8.0 > Automate generation of schema files > --- > > Key: SENTRY-1484 > URL: https://issues.apache.org/jira/browse/SENTRY-1484 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 1.8.0 >Reporter: Alexander Kolbasov >Priority: Minor > > The schema files for various DB engines are maintained manually. We should > think of some automated or semi-automated ways of creating this. Ideally we'd > like these auto-generated by Datanucleus and dumped for us. An alternative is > to use some macro engine to describe schemas and having some tool to > automatically generate correct SQL syntax for various DB engines. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1493) Evaluate performance impact of using repeatable-read vs read-committed for Sentry
[ https://issues.apache.org/jira/browse/SENTRY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1493: --- Affects Version/s: (was: sentry-ha-redesign) > Evaluate performance impact of using repeatable-read vs read-committed for > Sentry > - > > Key: SENTRY-1493 > URL: https://issues.apache.org/jira/browse/SENTRY-1493 > Project: Sentry > Issue Type: Task > Components: Sentry >Affects Versions: 1.7.0 >Reporter: Alexander Kolbasov >Priority: Minor > > SENTRY-1486 changes the isolation level from read-committed to repeatable > read. This task is about evaluating perf impact for different databases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1488) Create scripts that DBA can use to collect scale and usage stats
[
https://issues.apache.org/jira/browse/SENTRY-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1488:
---
Affects Version/s: (was: sentry-ha-redesign)
> Create scripts that DBA can use to collect scale and usage stats
>
>
> Key: SENTRY-1488
> URL: https://issues.apache.org/jira/browse/SENTRY-1488
> Project: Sentry
> Issue Type: New Feature
> Components: Sentry
>Affects Versions: 1.8.0
>Reporter: Anne Yu
>Assignee: Anne Yu
> Attachments: SENTRY-1488.0.patch, stats-1.png, stats-2.png
>
>
> We could create a script/tool subfolder so that can add side tools into it.
> For example, we could simply create a script that gives us a row count of
> every table in the Sentry database, plus the same thing for every table in
> the Hive Metastore database. That will give us info like: total number of
> tables, total number of roles, total permissions, etc.
> To start with:
> {code}
> #Roles
> #Permissions
> #Groups
> #Permissions per Role: avg, medium and max
> #Roles per Permission: avg, medium and max
> #Groups per role: avg, medium and max
> #Roles per group: avg, medium and max
> #Databases
> #Tables
> #Views
> #Partitions
> #Tables per Database: avg, medium and max
> #Views per Database: avg, medium and max
> #Partitions per Table: avg, medium and max
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.
[ https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1423: --- Issue Type: Sub-task (was: Bug) Parent: SENTRY-872 > Sentry HA Test: programmatic failover in a mini cluster env; also add some > test data. > - > > Key: SENTRY-1423 > URL: https://issues.apache.org/jira/browse/SENTRY-1423 > Project: Sentry > Issue Type: Sub-task > Components: Sentry, Test >Affects Versions: sentry-ha-redesign >Reporter: Anne Yu >Assignee: kalyan kumar kalvagadda > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1423.0-sentry-ha-redesign.patch, > SENTRY-1423.2-sentry-ha-redesign.patch, SENTRY-1423.3-sentry-ha-redesign.patch > > > .create role, grant privileges > .failover > .validate role and privileges. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.
[ https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov reassigned SENTRY-1423: -- Assignee: kalyan kumar kalvagadda > Sentry HA Test: programmatic failover in a mini cluster env; also add some > test data. > - > > Key: SENTRY-1423 > URL: https://issues.apache.org/jira/browse/SENTRY-1423 > Project: Sentry > Issue Type: Bug > Components: Sentry, Test >Affects Versions: sentry-ha-redesign >Reporter: Anne Yu >Assignee: kalyan kumar kalvagadda > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1423.0-sentry-ha-redesign.patch, > SENTRY-1423.2-sentry-ha-redesign.patch, SENTRY-1423.3-sentry-ha-redesign.patch > > > .create role, grant privileges > .failover > .validate role and privileges. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1423) Sentry HA Test: programmatic failover in a mini cluster env; also add some test data.
[ https://issues.apache.org/jira/browse/SENTRY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982480#comment-15982480 ] Alexander Kolbasov commented on SENTRY-1423: [~kkalyan] you are working on automated testing for client failover, you may see whether there is anything useful here. > Sentry HA Test: programmatic failover in a mini cluster env; also add some > test data. > - > > Key: SENTRY-1423 > URL: https://issues.apache.org/jira/browse/SENTRY-1423 > Project: Sentry > Issue Type: Bug > Components: Sentry, Test >Affects Versions: sentry-ha-redesign >Reporter: Anne Yu >Assignee: kalyan kumar kalvagadda > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1423.0-sentry-ha-redesign.patch, > SENTRY-1423.2-sentry-ha-redesign.patch, SENTRY-1423.3-sentry-ha-redesign.patch > > > .create role, grant privileges > .failover > .validate role and privileges. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1606) Sentry HDFS Sync should survive in presence of bad paths objects
[ https://issues.apache.org/jira/browse/SENTRY-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982474#comment-15982474 ] Alexander Kolbasov commented on SENTRY-1606: This is addressed as part of SENTRY-1687 > Sentry HDFS Sync should survive in presence of bad paths objects > - > > Key: SENTRY-1606 > URL: https://issues.apache.org/jira/browse/SENTRY-1606 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Currently when Sentry encounters any problem with the path object it fails to > construct a snapshot and the whole HDFS sync process breaks. > To make things more robust it should skip bad paths and continue creating the > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1606) Sentry HDFS Sync should survive in presence of bad paths objects
[ https://issues.apache.org/jira/browse/SENTRY-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1606: --- Issue Type: Sub-task (was: Bug) Parent: SENTRY-872 > Sentry HDFS Sync should survive in presence of bad paths objects > - > > Key: SENTRY-1606 > URL: https://issues.apache.org/jira/browse/SENTRY-1606 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Currently when Sentry encounters any problem with the path object it fails to > construct a snapshot and the whole HDFS sync process breaks. > To make things more robust it should skip bad paths and continue creating the > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SENTRY-1606) Sentry HDFS Sync should survive in presence of bad paths objects
[ https://issues.apache.org/jira/browse/SENTRY-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov reassigned SENTRY-1606: -- Assignee: Alexander Kolbasov > Sentry HDFS Sync should survive in presence of bad paths objects > - > > Key: SENTRY-1606 > URL: https://issues.apache.org/jira/browse/SENTRY-1606 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Currently when Sentry encounters any problem with the path object it fails to > construct a snapshot and the whole HDFS sync process breaks. > To make things more robust it should skip bad paths and continue creating the > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1606) Sentry HDFS Sync should survive in presence of bad paths objects
[ https://issues.apache.org/jira/browse/SENTRY-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1606: --- Affects Version/s: (was: 1.8.0) > Sentry HDFS Sync should survive in presence of bad paths objects > - > > Key: SENTRY-1606 > URL: https://issues.apache.org/jira/browse/SENTRY-1606 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov > > Currently when Sentry encounters any problem with the path object it fails to > construct a snapshot and the whole HDFS sync process breaks. > To make things more robust it should skip bad paths and continue creating the > snapshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1697) Deprecate feature flag for enabling notification log
[ https://issues.apache.org/jira/browse/SENTRY-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1697: --- Priority: Minor (was: Major) > Deprecate feature flag for enabling notification log > > > Key: SENTRY-1697 > URL: https://issues.apache.org/jira/browse/SENTRY-1697 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Alexander Kolbasov >Priority: Minor > Attachments: SENTRY-1697.001-sentry-ha-redesign.patch > > > We tried to use the feature flag to support old way of talking between HMS > and Sentry but it isn't quite supported and it isn't trivial to make it work, > so we should deprecate the feature flag. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1701) Improve retry handling for FullUpdateInitializer
[ https://issues.apache.org/jira/browse/SENTRY-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1701: --- Issue Type: Sub-task (was: Bug) Parent: SENTRY-872 > Improve retry handling for FullUpdateInitializer > > > Key: SENTRY-1701 > URL: https://issues.apache.org/jira/browse/SENTRY-1701 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov > > The retry code in FullUpdateInitializer isn't very clear and needs some > improvements as well as a unit test. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SENTRY-1671) Provide HMSFollower healthcheck (metric)
[ https://issues.apache.org/jira/browse/SENTRY-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov resolved SENTRY-1671. Resolution: Won't Fix We are not going to do it for now, may be later. We do not use any health checks now and adding them requires some thought. > Provide HMSFollower healthcheck (metric) > > > Key: SENTRY-1671 > URL: https://issues.apache.org/jira/browse/SENTRY-1671 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov > Labels: metrics, observability, supportability > Fix For: sentry-ha-redesign > > > We can have a Sentry which doesn't communicate properly with HMS. We need to > expose a heal-thcheck that shows whether HMSFollower is functioning. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1672) Expose HMS data via Sentry web UI
[ https://issues.apache.org/jira/browse/SENTRY-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1672: --- Affects Version/s: sentry-ha-redesign > Expose HMS data via Sentry web UI > - > > Key: SENTRY-1672 > URL: https://issues.apache.org/jira/browse/SENTRY-1672 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Priority: Minor > > It would be very useful (for debugging purposes) to expose current > notification ID and path snapshot via web UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1673) Improve error reporting from FullUpdateInitializer
[
https://issues.apache.org/jira/browse/SENTRY-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982461#comment-15982461
]
Alexander Kolbasov commented on SENTRY-1673:
This is addressed as part of SENTRY-1687
> Improve error reporting from FullUpdateInitializer
> --
>
> Key: SENTRY-1673
> URL: https://issues.apache.org/jira/browse/SENTRY-1673
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: kalyan kumar kalvagadda
>Priority: Critical
> Labels: bite-sized, newbie
> Fix For: sentry-ha-redesign
>
>
> I noticed the following error spilled from Sentry:
> {code}
> ERROR org.apache.sentry.hdfs.FullUpdateInitializer - Task did not complete
> successfully after 0 tries.
> {code}
> There is no stack trace or other details, also the {{0 tries}} is obviously
> incorrect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1679) HDFS tests configure MetastorePlugin which is gone
[
https://issues.apache.org/jira/browse/SENTRY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1679:
---
Priority: Minor (was: Major)
> HDFS tests configure MetastorePlugin which is gone
> --
>
> Key: SENTRY-1679
> URL: https://issues.apache.org/jira/browse/SENTRY-1679
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Vamsee Yarlagadda
>Priority: Minor
> Labels: bite-sized, newbie
> Fix For: sentry-ha-redesign
>
>
> In TestHDFSIntegrationBase#startHiveAndMetastore() there is:
> {code}
> hiveConf.set("sentry.metastore.plugins",
> "org.apache.sentry.hdfs.MetastorePlugin");
> {code}
> But we no longer have {{MetastorePlugin}}, so this should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1685: --- Labels: merge (was: ) > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li >Priority: Minor > Labels: merge > Fix For: sentry-ha-redesign > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1685) Port SENTRY-1489 to sentry-ha-redesign branch
[ https://issues.apache.org/jira/browse/SENTRY-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1685: --- Priority: Major (was: Minor) > Port SENTRY-1489 to sentry-ha-redesign branch > - > > Key: SENTRY-1685 > URL: https://issues.apache.org/jira/browse/SENTRY-1685 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: sentry-ha-redesign >Reporter: Alexander Kolbasov >Assignee: Na Li > Labels: merge > Fix For: sentry-ha-redesign > > > We need to port SENTRY-1489 to sentry-ha-redesign branch -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1687) FullUpdateInitializer can be more efficient
[
https://issues.apache.org/jira/browse/SENTRY-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Kolbasov updated SENTRY-1687:
---
Priority: Major (was: Minor)
> FullUpdateInitializer can be more efficient
> ---
>
> Key: SENTRY-1687
> URL: https://issues.apache.org/jira/browse/SENTRY-1687
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: sentry-ha-redesign
>Reporter: Alexander Kolbasov
>Assignee: Alexander Kolbasov
> Attachments: SENTRY-1687.001-sentry-ha-redesign.patch
>
>
> The FullUpdateInitializer follows the {{MetastoreCacheInitializer}}. It reads
> a bunch of information from HMS and uses Thrift structures to pass around,
> but in the end it just constructs {{Map}}. It uses
> concurrent fetches from HMS, but synchronizes a lot on common data structures
> to update them.
> I think that we can refactor all this code to make it faster and consume less
> memory. The idea is the following:
> Use background threads to collect Thrift results from HMS calls (database,
> table and partition data). Then we can use a single thread to construct the
> resulting update and return it without using intermediate Thrift methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SENTRY-1719) Implement alternative HMS/Sentry synchronization
Alexander Kolbasov created SENTRY-1719: -- Summary: Implement alternative HMS/Sentry synchronization Key: SENTRY-1719 URL: https://issues.apache.org/jira/browse/SENTRY-1719 Project: Sentry Issue Type: Sub-task Components: Sentry Affects Versions: sentry-ha-redesign Reporter: Alexander Kolbasov SENTRY-1640 describes the synchronization between HMS and Sentry. Unfortunately it depends on HMS features that are only available in future versions of Hive. We need to find some intermediate solution that will work until then and unblock testing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SENTRY-1427) Handle TGT renewals in HMSFollower
[ https://issues.apache.org/jira/browse/SENTRY-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1427: --- Component/s: Sentry > Handle TGT renewals in HMSFollower > -- > > Key: SENTRY-1427 > URL: https://issues.apache.org/jira/browse/SENTRY-1427 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin, Sentry >Affects Versions: sentry-ha-redesign >Reporter: Sravya Tirukkovalur >Assignee: Vamsee Yarlagadda > Fix For: sentry-ha-redesign > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SENTRY-1427) Handle TGT renewals in HMSFollower
[ https://issues.apache.org/jira/browse/SENTRY-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982450#comment-15982450 ] Alexander Kolbasov commented on SENTRY-1427: I think that TGT renewals only work for some time. Will the current code handle obtaining a new Kerberos credential when this expires? > Handle TGT renewals in HMSFollower > -- > > Key: SENTRY-1427 > URL: https://issues.apache.org/jira/browse/SENTRY-1427 > Project: Sentry > Issue Type: Sub-task > Components: Hdfs Plugin >Affects Versions: sentry-ha-redesign >Reporter: Sravya Tirukkovalur >Assignee: Vamsee Yarlagadda > Fix For: sentry-ha-redesign > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
