[
https://issues.apache.org/jira/browse/HIVE-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922869#comment-13922869
]
Xuefu Zhang commented on HIVE-6468:
-----------------------------------
I agree that guard against this is good. Just curious, however, why a http get
request would put HS2 in OOM? It's understandable that HS2 doesn't understand
the request, but how it runs out of memory seems interesting.
> HS2 out of memory error when curl sends a get request
> -----------------------------------------------------
>
> Key: HIVE-6468
> URL: https://issues.apache.org/jira/browse/HIVE-6468
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.12.0
> Environment: Centos 6.3, hive 12, hadoop-2.2
> Reporter: Abin Shahab
> Assignee: Navis
> Attachments: HIVE-6468.1.patch.txt
>
>
> We see an out of memory error when we run simple beeline calls.
> (The hive.server2.transport.mode is binary)
> curl localhost:10000
> Exception in thread "pool-2-thread-8" java.lang.OutOfMemoryError: Java heap
> space
> at
> org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:181)
> at
> org.apache.thrift.transport.TSaslServerTransport.handleSaslStartMessage(TSaslServerTransport.java:125)
> at
> org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:253)
> at
> org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
> at
> org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:189)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
