You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ashutosh Bapat (JIRA)" <ji...@apache.org> on 2018/12/10 05:13:00 UTC
[jira] [Assigned] (HIVE-21022) Fix remote metastore tests which use
ZooKeeper
[ https://issues.apache.org/jira/browse/HIVE-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Bapat reassigned HIVE-21022:
-------------------------------------
> Fix remote metastore tests which use ZooKeeper
> ----------------------------------------------
>
> Key: HIVE-21022
> URL: https://issues.apache.org/jira/browse/HIVE-21022
> Project: Hive
> Issue Type: Bug
> Components: Tests
> Affects Versions: 4.0.0
> Reporter: Ashutosh Bapat
> Assignee: Ashutosh Bapat
> Priority: Major
> Fix For: 4.0.0
>
>
> Per [~vgarg]'s comment on HIVE-20794 at https://issues.apache.org/jira/browse/HIVE-20794?focusedCommentId=16714093&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16714093, the remote metatstore tests using ZooKeeper are flaky. They are failing with error "Got exception: org.apache.zookeeper.KeeperException$NoNodeException KeeperErrorCode = NoNode for /hs2mszktest".
> Both of these tests are using the same root namespace and hence the reason for this failure could be that the root namespace becomes unavailable to one test when the other drops it. The drop seems to be happening automatically through TestingServer code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)