[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&focusedCommentId=15996224#comment-15996224 ] Na Li commented on SENTRY-1649: --- The changes are 1. move starting HMSFollower from SentrySe

[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.037-sentry-ha-redesign.patch v37. create HMSFollower in startHMSFollower. Update based

[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&focusedCommentId=15996170#comment-15996170 ] 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

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Attachment: SENTRY-1649.036-sentry-ha-redesign.patch Patch v.35 with code review comm

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

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Patch Available (was: Open) > Initialize HMSFollower when sentry server actu

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

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1649: --- Status: Open (was: Patch Available) > Initialize HMSFollower when sentry server actu

[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&focusedCommentId=15996045#comment-15996045 ] Alexander Kolbasov commented on SENTRY-1649: [~lina.li] There are a lot of up

[jira] [Comment Edited] (SENTRY-1747) HMSFollower shouldn't create local hive during tests

[ https://issues.apache.org/jira/browse/SENTRY-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995803#comment-15995803 ] Alexander Kolbasov edited comment on SENTRY-1747 at 5/3/17 10:23 PM: --

[jira] [Commented] (SENTRY-1747) HMSFollower shouldn't create local hive during tests

[ https://issues.apache.org/jira/browse/SENTRY-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995803#comment-15995803 ] Alexander Kolbasov commented on SENTRY-1747: As noted by [~spena] a better wa

[jira] [Updated] (SENTRY-1747) HMSFollower shouldn't create local hive during tests

[ https://issues.apache.org/jira/browse/SENTRY-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1747: --- Status: Open (was: Patch Available) > HMSFollower shouldn't create local hive during

[jira] [Updated] (SENTRY-1747) HMSFollower shouldn't create local hive during tests

[ https://issues.apache.org/jira/browse/SENTRY-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1747: --- Attachment: (was: SENTRY-1747.001-sentry-ha-redesign.patch) > HMSFollower shouldn

[jira] [Updated] (SENTRY-1723) HDFS e2e tests should wait for HMSFollower to start

[ https://issues.apache.org/jira/browse/SENTRY-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1723: --- Summary: HDFS e2e tests should wait for HMSFollower to start (was: Flaky test TestHD

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

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

[jira] [Commented] (SENTRY-1723) Flaky test TestHDFSIntegrationEnd2End

[ https://issues.apache.org/jira/browse/SENTRY-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995669#comment-15995669 ] Na Li commented on SENTRY-1723: --- The initial delay to schedule HMSFollower being 6 ms

[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&focusedCommentId=15995643#comment-15995643 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

[jira] [Comment Edited] (SENTRY-1630) out of sequence error in HMSFollower

[ https://issues.apache.org/jira/browse/SENTRY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995632#comment-15995632 ] kalyan kumar kalvagadda edited comment on SENTRY-1630 at 5/3/17 8:44 PM: --

[jira] [Commented] (SENTRY-1630) out of sequence error in HMSFollower

[ https://issues.apache.org/jira/browse/SENTRY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995632#comment-15995632 ] kalyan kumar kalvagadda commented on SENTRY-1630: - I have not tested late

[jira] [Commented] (SENTRY-1630) out of sequence error in HMSFollower

[ https://issues.apache.org/jira/browse/SENTRY-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995624#comment-15995624 ] Lei (Eddy) Xu commented on SENTRY-1630: --- Hi, [~kkalyan], [~akolb] Do you see this i

[jira] [Resolved] (SENTRY-1666) TestHDFSIntegrationAdvanced timeouts on sentry-ha-redesign branch

[ https://issues.apache.org/jira/browse/SENTRY-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei (Eddy) Xu resolved SENTRY-1666. --- Resolution: Cannot Reproduce [~spena] I could not reproduce this anymore. I will close this f

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

[ 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.001-sentry-ha-redesign.patch > Avoid randomizing th

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

[ https://issues.apache.org/jira/browse/SENTRY-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1709: Status: Patch Available (was: In Progress) > Avoid randomizing the servers

[jira] [Updated] (SENTRY-1695) Waiting for HMS notifications from Thrift should be interruptible

[ https://issues.apache.org/jira/browse/SENTRY-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kolbasov updated SENTRY-1695: --- Resolution: Fixed Fix Version/s: sentry-ha-redesign Status: Resolved

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

[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995497#comment-15995497 ] Sergio Peña commented on SENTRY-1743: - Can you submit the patch to the review board?

[jira] [Commented] (SENTRY-1666) TestHDFSIntegrationAdvanced timeouts on sentry-ha-redesign branch

[ https://issues.apache.org/jira/browse/SENTRY-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995481#comment-15995481 ] Sergio Peña commented on SENTRY-1666: - [~eddyxu] Is this reproducible on your side? T

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

[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995456#comment-15995456 ] Alexander Kolbasov commented on SENTRY-1743: [~spena] The patch is for the ma

[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: SENTRY-1669.001-sentry-ha-redesign.patch > HMSFollower should r

[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: (was: SENTRY-1669.001-sentry-ha-redesign.patch) > HMSFollow

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

[ https://issues.apache.org/jira/browse/SENTRY-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995418#comment-15995418 ] Sergio Peña commented on SENTRY-1743: - [~akolb] I cannot apply this patch on the sent

[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&focusedCommentId=15995373#comment-15995373 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: (was: SENTRY-1669.001-sentry-ha-redesign.patch) > HMSFollow

[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: SENTRY-1669.001-sentry-ha-redesign.patch > HMSFollower should r

[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&focusedCommentId=15995356#comment-15995356 ] Hadoop QA commented on SENTRY-1669: --- Here are the results of testing the latest attachm

[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Attachment: SENTRY-1669.001-sentry-ha-redesign.patch > HMSFollower should r

[jira] [Updated] (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:all-tabpanel ] kalyan kumar kalvagadda updated SENTRY-1669: Status: Patch Available (was: In Progress) > HMSFollower should read curre

[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&focusedCommentId=15995254#comment-15995254 ] 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

[ https://issues.apache.org/jira/browse/SENTRY-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-1649: -- Attachment: SENTRY-1649.035-sentry-ha-redesign.patch v35. start HMSFollower sooner and check needHiveSnapshot a

[jira] [Updated] (SENTRY-1730) Remove FileInputStream/FileOutputStream

[ https://issues.apache.org/jira/browse/SENTRY-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-1730: Resolution: Fixed Status: Resolved (was: Patch Available) > Remove FileInp

[jira] [Commented] (SENTRY-1730) Remove FileInputStream/FileOutputStream

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

[jira] [Updated] (SENTRY-1730) Remove FileInputStream/FileOutputStream

[ https://issues.apache.org/jira/browse/SENTRY-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-1730: Attachment: SENTRY-1730.patch Updating patch. > Remove FileInputStream/FileOutputS

[jira] [Updated] (SENTRY-1730) Remove FileInputStream/FileOutputStream

[ https://issues.apache.org/jira/browse/SENTRY-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SENTRY-1730: Attachment: (was: SENTRY-1730.patch) > Remove FileInputStream/FileOutputStream