[
https://issues.apache.org/jira/browse/HIVE-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048501#comment-14048501
]
Navis commented on HIVE-6468:
-----------------------------
1. ok, sure.
2. just wanted not to miss any runtime exceptions. Not much differences in
action.
3. saslServer is final field. So must be assigned to null.
4. Thought wrapping AuthenticationException into LoginException is not that
useful.
For PlainSaslHelper, most of codes are copied as-is from
TSaslServerTransport.Factory. So, I believe there's a reason for weak
references.
For socket timeout, there are other issues for it (HIVE-6679, etc.).
> 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)
