[
https://issues.apache.org/jira/browse/HIVE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458001#comment-13458001
]
Carl Steinbach commented on HIVE-3469:
--------------------------------------
@Rohit: We could probably adjust the layering of these two methods slightly,
but I doubt that it would accomplish much in terms of improving performance,
mainly because this operation is done once per connection, and we expect
clients to spend most of their time doing something else. If HIVE-2937 fixes
the concurrency issue then I think we should probably mark this ticket as a
duplicate of 2937 and backport 2937 to 0.9.
> When new hive cluster is started, hive jdbc client hangs.
> ---------------------------------------------------------
>
> Key: HIVE-3469
> URL: https://issues.apache.org/jira/browse/HIVE-3469
> Project: Hive
> Issue Type: Bug
> Components: Clients, Metastore, Thrift API
> Environment: Hadoop-2.0.1 + Hive-0.9.0
> Reporter: rohithsharma
>
> The scenario is as follows :
> For the new hive cluster , when multiple hive client is getting the
> connection for hive server , there are 3 problems in metastore , hive client.
> 1. Since the derby is booted at first connection, multiple client try to
> create database.One of the client succeed and another one throw exception
> because of *unique primary constraint* in metatables.
> 2. Once the Runtime exception is throw, the hive client which is made
> connection request will hang forever.
> 3. Potentially "ConcurrentModificationException" is thrown by JDOQuery.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
