hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <>
Subject [jira] [Commented] (HIVE-6468) HS2 out of memory error when curl sends a get request
Date Tue, 18 Mar 2014 22:54:44 GMT


Lefty Leverenz commented on HIVE-6468:

Thanks, I put it in a warning box with this wording:  "In remote mode HiveServer2 only accepts
valid Thrift calls – do not attempt to call it via http or telnet (HIVE-6468)."

Should it also explain that HS2 will die, or is that just until this jira's patch gets added?
 Readers can click the link to this jira if they want to know the reason for the warning,
but we could make it explicit if you think that's better.

By the way, *hive.server2.sasl.message.limit* needs some user doc.  It can go in a
comment for now, or in a release note, until we know when HIVE-6037 will get committed.

Quick ref:

* [new warning in Beeline – New Command Line Shell |–NewCommandLineShell]
* [page history:  new changes |]

> HS2 out of memory error when curl sends a get request
> -----------------------------------------------------
>                 Key: HIVE-6468
>                 URL:
>             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(
> 	at org.apache.thrift.transport.TSaslServerTransport.handleSaslStartMessage(
> 	at
> 	at
> 	at org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(
> 	at org.apache.thrift.server.TThreadPoolServer$
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at

This message was sent by Atlassian JIRA

View raw message