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

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996288#comment-15996288 ] Hadoop QA commented on SENTRY-1649: --- Here are the results of testing the latest attachm

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

2017-05-04 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.035-sentry-ha-redesign.patch v35. To verify it works > Initialize HMSFollower when sen

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

2017-05-04 Thread Na Li (JIRA)
[ 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.037-sentry-ha-redesign.patch v37. local test succeeds. check if build works > Initiali

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

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997135#comment-15997135 ] Hadoop QA commented on SENTRY-1649: --- Here are the results of testing the latest attachm

[jira] [Created] (SENTRY-1748) Sentry HA: for testing purposes, allow the client to be configured to deterministically choose which Sentry server to use

2017-05-04 Thread Ben Iglauer (JIRA)
Ben Iglauer created SENTRY-1748: --- Summary: Sentry HA: for testing purposes, allow the client to be configured to deterministically choose which Sentry server to use Key: SENTRY-1748 URL: https://issues.apache.org/ji

[jira] [Assigned] (SENTRY-1748) Sentry HA: for testing purposes, allow the client to be configured to deterministically choose which Sentry server to use

2017-05-04 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda reassigned SENTRY-1748: --- Assignee: kalyan kumar kalvagadda > Sentry HA: for testing purposes,

[jira] [Created] (SENTRY-1749) Sentry fails to setup secure connection to HMS if the local running unix user is missing active tgt

2017-05-04 Thread Vamsee Yarlagadda (JIRA)
Vamsee Yarlagadda created SENTRY-1749: - Summary: Sentry fails to setup secure connection to HMS if the local running unix user is missing active tgt Key: SENTRY-1749 URL: https://issues.apache.org/jira/browse/

[jira] [Commented] (SENTRY-1749) Sentry fails to setup secure connection to HMS if the local running unix user is missing active tgt

2017-05-04 Thread Vamsee Yarlagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997493#comment-15997493 ] Vamsee Yarlagadda commented on SENTRY-1749: --- Some analysis on this problem: Lo

[jira] [Updated] (SENTRY-1749) Sentry fails to setup secure connection to HMS if the local running unix user is missing active tgt

2017-05-04 Thread Vamsee Yarlagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsee Yarlagadda updated SENTRY-1749: -- Status: Patch Available (was: Open) > Sentry fails to setup secure connection to HMS i

[jira] [Updated] (SENTRY-1749) Sentry fails to setup secure connection to HMS if the local running unix user is missing active tgt

2017-05-04 Thread Vamsee Yarlagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsee Yarlagadda updated SENTRY-1749: -- Attachment: SENTRY-1749.01-sentry-ha-redesign.patch > Sentry fails to setup secure conn

[jira] [Updated] (SENTRY-1709) Avoid randomizing the servers at client side based on configuration.

2017-05-04 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1709: Attachment: SENTRY-1709.002-sentry-ha-redesign.patch > Avoid randomizing th

[jira] [Updated] (SENTRY-1749) Sentry to use keytab supplied instead of local unix user tgt for connecting to HMS

2017-05-04 Thread Vamsee Yarlagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsee Yarlagadda updated SENTRY-1749: -- Summary: Sentry to use keytab supplied instead of local unix user tgt for connecting to

[jira] [Updated] (SENTRY-1749) HMSFollower uses incorrect keytab for HMS connection

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1749: --- Summary: HMSFollower uses incorrect keytab for HMS connection (was: Sentry to use ke

[jira] [Updated] (SENTRY-1749) HMSFollower uses incorrect keytab for HMS connection

2017-05-04 Thread Vamsee Yarlagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsee Yarlagadda updated SENTRY-1749: -- Resolution: Fixed Fix Version/s: sentry-ha-redesign Status: Resolved

[jira] [Updated] (SENTRY-1709) Avoid randomizing the servers at client side based on configuration.

2017-05-04 Thread kalyan kumar kalvagadda (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1709: Attachment: SENTRY-1709.003-sentry-ha-redesign.patch > Avoid randomizing th

[jira] [Commented] (SENTRY-1749) HMSFollower uses incorrect keytab for HMS connection

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997594#comment-15997594 ] Hadoop QA commented on SENTRY-1749: --- Here are the results of testing the latest attachm

[jira] [Resolved] (SENTRY-1748) Sentry HA: for testing purposes, allow the client to be configured to deterministically choose which Sentry server to use

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov resolved SENTRY-1748. Resolution: Duplicate > Sentry HA: for testing purposes, allow the client to be con

[jira] [Commented] (SENTRY-1709) Avoid randomizing the servers at client side based on configuration.

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997665#comment-15997665 ] Hadoop QA commented on SENTRY-1709: --- Here are the results of testing the latest attachm

[jira] [Commented] (SENTRY-1709) Avoid randomizing the servers at client side based on configuration.

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997670#comment-15997670 ] Hadoop QA commented on SENTRY-1709: --- Here are the results of testing the latest attachm

[jira] [Updated] (SENTRY-1276) Bump hadoop version to 2.6.1

2017-05-04 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1276: Fix Version/s: 1.8.0 > Bump hadoop version to 2.6.1 > > > Key:

[jira] [Updated] (SENTRY-1276) Bump hadoop version to 2.6.1

2017-05-04 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1276: Affects Version/s: 1.7.0 > Bump hadoop version to 2.6.1 > > >

[jira] [Updated] (SENTRY-1276) Bump hadoop version to 2.6.1

2017-05-04 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao updated SENTRY-1276: Resolution: Fixed Status: Resolved (was: Patch Available) > Bump hadoop version to 2.6.1 > ---

[jira] [Commented] (SENTRY-1276) Bump hadoop version to 2.6.1

2017-05-04 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997750#comment-15997750 ] Hao Hao commented on SENTRY-1276: - Current hadoop version is 2.7.2. Resolved this ticket.

[jira] [Resolved] (SENTRY-1276) Bump hadoop version to 2.6.1

2017-05-04 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao resolved SENTRY-1276. - Resolution: Not A Problem > Bump hadoop version to 2.6.1 > > >

[jira] [Reopened] (SENTRY-1276) Bump hadoop version to 2.6.1

2017-05-04 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reopened SENTRY-1276: - > Bump hadoop version to 2.6.1 > > > Key: SENTRY-1276 >

[jira] [Updated] (SENTRY-1709) Avoid randomizing the servers at client side based on configuration.

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1709: --- Resolution: Fixed Status: Resolved (was: Patch Available) [~kkalyan] Thank y

[jira] [Commented] (SENTRY-1740) Deadlock when handling GM privileges

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997800#comment-15997800 ] Alexander Kolbasov commented on SENTRY-1740: This isn't related to SENTRY-174

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Status: Open (was: Patch Available) > Two SentryStore instances are one too many > -

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Attachment: SENTRY-1743.001.patch > Two SentryStore instances are one too many >

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Status: Patch Available (was: Open) > Two SentryStore instances are one too many > -

[jira] [Commented] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997805#comment-15997805 ] Hadoop QA commented on SENTRY-1743: --- Here are the results of testing the latest attachm

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

2017-05-04 Thread Na Li (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.039-sentry-ha-redesign.patch v39. fix unit test TestDbSentryOnFailureHookLoading. Incre

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Status: Patch Available (was: Open) > Two SentryStore instances are one too many > -

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Attachment: SENTRY-1743.001.patch > Two SentryStore instances are one too many >

[jira] [Updated] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Alexander Kolbasov (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1743: --- Status: Open (was: Patch Available) > Two SentryStore instances are one too many > -

[jira] [Commented] (SENTRY-1743) Two SentryStore instances are one too many

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997817#comment-15997817 ] Hadoop QA commented on SENTRY-1743: --- Here are the results of testing the latest attachm

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

2017-05-04 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997854#comment-15997854 ] Hadoop QA commented on SENTRY-1649: --- Here are the results of testing the latest attachm