I have had the same problem and bouncing the Hive server temporarily alleviates this.
Abe On Thu, Apr 30, 2015 at 2:20 AM, Shady Xu <shad...@gmail.com> wrote: > I found the patch here https://issues.apache.org/jira/browse/HIVE-9119. > But upgrading is the last thing we want to do. > > Also, I found another solution which changes the hive.server2.enable.doAs > property > to false to use the same user to do the hive operations. But I'm not sure > whether a user here is the same with a `client` described in the issue. > > 2015-04-30 11:01 GMT+08:00 Shady Xu <shad...@gmail.com>: > >> Thanks. But is there any other solution besides upgrading? >> >> 2015-04-30 10:55 GMT+08:00 Xuefu Zhang <xzh...@cloudera.com>: >> >>> This is a known issue and has been fixed in later releases. >>> >>> --Xuefu >>> >>> On Wed, Apr 29, 2015 at 7:44 PM, Shady Xu <shad...@gmail.com> wrote: >>> >>>> Recently I found in the zookeeper log that there were too many client >>>> connections and it was hive that was establishing more and more >>>> connections. >>>> >>>> I modified the max client connection property in zookeeper and that >>>> fixed the problem, temporarily. But the connections hive made to zookeeper >>>> were still growing. >>>> >>>> It seems that hive does not use a connection pool to reuse the >>>> connections. So how can I configure to reduce the connections? >>>> >>>> P.S. >>>> I am using Hive-0.12.0 >>>> >>> >>> >> >
