[
https://issues.apache.org/jira/browse/HIVE-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879753#comment-15879753
]
Mohit Sabharwal commented on HIVE-16016:
----------------------------------------
Thanks for the review [~sershe]! The separate RS in DbNotificationListener is
used by the CleanerThread (which gets created by DbNotificationListener)
outside the TThreadPoolServer/hmshandler threadpool.
Thanks, [~vgumashta]. Looks like your patch already had a successful test run.
Please commit your patch. I'll move the test portion of this patch over to
HIVE-15305 (where it really belongs).
> Use same PersistenceManager for metadata and notification
> ---------------------------------------------------------
>
> Key: HIVE-16016
> URL: https://issues.apache.org/jira/browse/HIVE-16016
> Project: Hive
> Issue Type: Bug
> Components: repl
> Reporter: Mohit Sabharwal
> Assignee: Mohit Sabharwal
> Attachments: HIVE-16016.patch
>
>
> HIVE-13966 added to support for persisting notification in the same JDO
> transaction as the metadata event. However, the notification is currently
> added using a different ObjectStore object from the one used to persist the
> metadata event.
> The notification is added using the ObjectStore constructed in
> DbNotificationListener, whereas the metadata event is added via the thread
> local ObjectStore (i.e. threadLocalMS in HiveMetaStore.HMSHandler).
> As a result, different PersistenceManagers (different transactions) are used
> to persist notification and metadata events.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
