[ https://issues.apache.org/jira/browse/SENTRY-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516114#comment-15516114 ]
Hadoop QA commented on SENTRY-1463: ----------------------------------- Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12830000/SENTRY-1463.003-sentry-ha-redesign.patch against sentry-ha-redesign. {color:red}Overall:{color} -1 due to 2 errors {color:red}ERROR:{color} mvn test exited 1 {color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.dbprovider.TestConcurrentClients Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/2034/console This message is automatically generated. > Ensure HMS point-in-time snapshot consistency > --------------------------------------------- > > Key: SENTRY-1463 > URL: https://issues.apache.org/jira/browse/SENTRY-1463 > Project: Sentry > Issue Type: Sub-task > Components: Sentry > Affects Versions: sentry-ha-redesign > Reporter: Hao Hao > Assignee: Hao Hao > Fix For: sentry-ha-redesign > > Attachments: SENTRY-1463.001-sentry-ha-redesign.patch, > SENTRY-1463.002-sentry-ha-redesign.patch, > SENTRY-1463.003-sentry-ha-redesign.patch > > > During HMSFollower start up, when retrieving HMS full snapshot, also need to > ensure point-in-time snapshot consistency. > It should be: > * Read current HMS notification ID_initial > * Read HMS metadata state > * Read current notification ID_new > * If ID_initial != ID_new then discard the current state and goto 1. > Use configurable property: sentry.hms.snapshot.retries.max.count for max > number of retry. > Ideally, during fetching full snapshot, there should be no write activity on > the HMS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)