[
https://issues.apache.org/jira/browse/HIVE-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095083#comment-14095083
]
Harsh J commented on HIVE-6468:
-------------------------------
It would also help add a check for the payload length detected as < 0 (i.e.
negative number) aside of an upper message cap.
It also seems Thrift is doing this incorrectly so we should rather fix it there
and consume it in, than duplicate its code at our end. I found this JIRA after
I'd filed THRIFT-2660.
> 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, HIVE-6468.2.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)
