[jira] [Updated] (SENTRY-1703) Solr-Sentry in kerberos mode makes too many KDC requests and returns unauthorized on KDC timeout

[ https://issues.apache.org/jira/browse/SENTRY-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar I updated SENTRY-1703: - Attachment: solr-sentry-test-master.zip > Solr-Sentry in kerberos mode makes too many KDC requests and

[jira] [Updated] (SENTRY-1703) Solr-Sentry in kerberos mode makes too many KDC requests and returns unauthorized on KDC timeout

[ https://issues.apache.org/jira/browse/SENTRY-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar I updated SENTRY-1703: - Attachment: solr-sentry-test.zip > Solr-Sentry in kerberos mode makes too many KDC requests and returns

[jira] [Updated] (SENTRY-1703) Solr-Sentry in kerberos mode makes too many KDC requests and returns unauthorized on KDC timeout

[ https://issues.apache.org/jira/browse/SENTRY-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tushar I updated SENTRY-1703: - Attachment: (was: solr-sentry-test-master.zip) > Solr-Sentry in kerberos mode makes too many KDC

[jira] [Commented] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone

[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975833#comment-15975833 ] Lei (Eddy) Xu commented on SENTRY-1643: --- Looks promising. Thanks for this information,

[jira] [Commented] (SENTRY-1643) AutoIncrement ChangeID of MSentryPermChange/MSentryPathChange may be error-prone

[ https://issues.apache.org/jira/browse/SENTRY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975820#comment-15975820 ] Na Li commented on SENTRY-1643: --- based on

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

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.023-sentry-ha-redesign.patch create HMSFollower in startHMSFollower and await

[jira] [Commented] (SENTRY-1706) Remove value-strategy for delta change tables.

[ https://issues.apache.org/jira/browse/SENTRY-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975777#comment-15975777 ] Lei (Eddy) Xu commented on SENTRY-1706: --- It is interesting that, after removing the value strategy

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975698#comment-15975698 ] Na Li commented on SENTRY-1669: --- [~kkalyan] Can you be more specific on what else to change to make sure

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975688#comment-15975688 ] kalyan kumar kalvagadda commented on SENTRY-1669: - There will be some more changes need

[jira] [Comment Edited] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975688#comment-15975688 ] kalyan kumar kalvagadda edited comment on SENTRY-1669 at 4/19/17 10:45 PM:

[jira] [Assigned] (SENTRY-1362) add sentry ha e2e test back accommodating to the re-design

[ https://issues.apache.org/jira/browse/SENTRY-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda reassigned SENTRY-1362: --- Assignee: kalyan kumar kalvagadda > add sentry ha e2e test back

[jira] [Assigned] (SENTRY-1424) Sentry HA client tests: master jira for all client related tests (retry, concurrency, correct exceptions etc.)

[ https://issues.apache.org/jira/browse/SENTRY-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda reassigned SENTRY-1424: --- Assignee: kalyan kumar kalvagadda > Sentry HA client tests: master

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975452#comment-15975452 ] Na Li commented on SENTRY-1674: --- There are two things to clarify. "Let's focus on this issue. This issue

[jira] [Commented] (SENTRY-1669) HMSFollower should read current processed notification ID from database every time it runs

[ https://issues.apache.org/jira/browse/SENTRY-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975436#comment-15975436 ] Na Li commented on SENTRY-1669: --- Can be solved by changes in SENTRY-1649 > HMSFollower should read current

[jira] [Commented] (SENTRY-1671) Provide HMSFollower healthcheck (metric)

[ https://issues.apache.org/jira/browse/SENTRY-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975430#comment-15975430 ] Mathew Crocker commented on SENTRY-1671: [~akolb] is there a specific metric you're trying to

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975410#comment-15975410 ] kalyan kumar kalvagadda commented on SENTRY-1674: - [~lina...@cloudera.com] You are taking

[jira] [Updated] (SENTRY-1686) Port SENTRY-1548 to sentry-ha-redesign branch

[ https://issues.apache.org/jira/browse/SENTRY-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1686: Resolution: Fixed Status: Resolved (was: Patch Available) > Port

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975382#comment-15975382 ] Na Li commented on SENTRY-1674: --- There is no conflict between Sentry-1674 and the work around by Hao at

[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=15975374#comment-15975374 ] Hadoop QA commented on SENTRY-1593: --- Here are the results of testing the latest attachment

[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.009-sentry-ha-redesign.patch) >

[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.009-sentry-ha-redesign.patch > Implement client

[jira] [Commented] (SENTRY-1678) Add test class to test refactored refactored config code

[ https://issues.apache.org/jira/browse/SENTRY-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15975176#comment-15975176 ] Hadoop QA commented on SENTRY-1678: --- Here are the results of testing the latest attachment

[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=15975035#comment-15975035 ] Hadoop QA commented on SENTRY-1593: --- Here are the results of testing the latest attachment

[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.009-sentry-ha-redesign.patch) >

[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=15975028#comment-15975028 ] kalyan kumar kalvagadda commented on SENTRY-1593: - [~akolb] Attached the latest class

[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: service_client_class_diagram_latest_v1.png > Implement client

[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=15975004#comment-15975004 ] Hadoop QA commented on SENTRY-1649: --- Here are the results of testing the latest attachment

[jira] [Updated] (SENTRY-1678) Add test class to test refactored refactored config code

[ https://issues.apache.org/jira/browse/SENTRY-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1678: Status: Patch Available (was: In Progress) > Add test class to test

[jira] [Updated] (SENTRY-1678) Add test class to test refactored refactored config code

[ https://issues.apache.org/jira/browse/SENTRY-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1678: Attachment: SENTRY-1678.001-sentry-ha-redesign.patch > Add test class to

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

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.022-sentry-ha-redesign.patch move start HMSFollower at the start of runServer(). v22

[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=15974749#comment-15974749 ] Na Li commented on SENTRY-1649: --- After moving starting HMSfollower to end of runServer(). the following

[jira] [Commented] (SENTRY-1674) HMSFollower shouldn't print the same value of notification ID multiple times

[ https://issues.apache.org/jira/browse/SENTRY-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974572#comment-15974572 ] kalyan kumar kalvagadda commented on SENTRY-1674: - [~lina...@cloudera.com] I'm fine with