[
https://issues.apache.org/jira/browse/HIVE-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057396#comment-13057396
]
Frank LoVecchio commented on HIVE-80:
-------------------------------------
We have tested multiple client connections submitting jobs rapidly to a single
hiveserver (running on a Brisk implementation); I would not recommend doing
this unless you have a que of some sort on your end. Otherwise, you will see
this:
ERROR in runJob
org.apache.thrift.transport.TTransportException: java.net.ConnectException:
Connection refused
Has anyone used multiple hiveservers for managing multiple connections?
(something like Amazon's cloud map/reduce, where they spin up a temporary
instance?)
Thanks
> Add testcases for concurrent query execution
> --------------------------------------------
>
> Key: HIVE-80
> URL: https://issues.apache.org/jira/browse/HIVE-80
> Project: Hive
> Issue Type: Test
> Components: Query Processor, Server Infrastructure
> Reporter: Raghotham Murthy
> Assignee: Arvind Prabhakar
> Priority: Critical
> Labels: concurrency
> Attachments: hive_input_format_race-2.patch
>
>
> Can use one driver object per query.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
