You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/05/05 14:56:04 UTC
[jira] [Created] (SENTRY-1751) HMSFollower should not persist empty
full snapshot
Na Li created SENTRY-1751:
-----------------------------
Summary: HMSFollower should not persist empty full snapshot
Key: SENTRY-1751
URL: https://issues.apache.org/jira/browse/SENTRY-1751
Project: Sentry
Issue Type: Bug
Components: Sentry
Affects Versions: sentry-ha-redesign
Reporter: Na Li
When HMSFollower gets empty full snapshot, it should not persist it in SentryStore.
Right now, it persists the empty full snapshot, and causes default AuthzObj saved in SentryStore. When another empty full snapshot is persisted, exception occurs.
2017-05-03 09:58:42,209 (pool-5-thread-1) [ERROR - org.apache.sentry.service.thrift.HMSFollower.run(HMSFollower.java:304)] Caught unexpected exception in HMSFollower! Caused by: AuthzObj: default already exists
org.apache.sentry.core.common.exception.SentryAlreadyExistsException: AuthzObj: default already exists
at org.apache.sentry.provider.db.service.persistent.SentryStore.createAuthzPathsMappingCore(SentryStore.java:2541)
at org.apache.sentry.provider.db.service.persistent.SentryStore.access$3000(SentryStore.java:101)
at org.apache.sentry.provider.db.service.persistent.SentryStore$42.execute(SentryStore.java:2515)
at org.apache.sentry.provider.db.service.persistent.TransactionManager.executeTransaction(TransactionManager.java:114)
at org.apache.sentry.provider.db.service.persistent.TransactionManager.executeTransactionWithRetry(TransactionManager.java:181)
at org.apache.sentry.provider.db.service.persistent.SentryStore.persistFullPathsImage(SentryStore.java:2511)
at org.apache.sentry.service.thrift.HMSFollower.run(HMSFollower.java:269)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)