Increasing hive.server2.thrift.max.worker.threads from default 500

[#1]

Hi,

What are the implications of increasing the

hive.server2.thrift.max.worker.threads from default 500, other than lot more connections on the Production Oracle database?

Thanks,

Kiran

[#2]

@kerra

I have increased hive.server2.thrift.max.worker.threads from default 500 to 1500 because of one issue with WinSQL Lite which was taking huge connection thread because of some bug in WinSQL Lite. What I have faced is when the connections threads reached 500 it was not allowing any new users to connect to Hiveserver2 using beeline. So I have increased it from 500 to 1500 to avoid this problem but usually, this will not happen if you are connected through beeline on edge node. 500 threads should be good enough to handle for one HiveServer2.

Command to check number of threads on Hiveserver2 node:

jstack -l <HiveServere2_ProccessId> | grep  ".Thread.Stat" | wc -l

Hope this helps you.

[#3]

The recommended approach is to add another Hiveserver2 on another machine. Increasing the thread count will help in the short term, but is not the recommended solution.