hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Muraru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11052) Sending random data crashes thrift service
Date Wed, 23 Apr 2014 21:36:16 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978941#comment-13978941
] 

Adrian Muraru commented on HBASE-11052:
---------------------------------------

Note that thrift 0.9.0 removes (weird!) the message limit support in TBinaryProtocol (THRIFT-820),
so for 0.95 onwards we should consider configuring HThrift server to use compact/framed transport
by default to avoid the OOM.


> Sending random data crashes thrift service
> ------------------------------------------
>
>                 Key: HBASE-11052
>                 URL: https://issues.apache.org/jira/browse/HBASE-11052
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>    Affects Versions: 0.98.1, 1.0.0, 0.94.18
>            Reporter: Adrian Muraru
>         Attachments: HBASE-11052.v1.patch
>
>
> Upstream thrift library has a know issue (THRIFT-601) causing the thrift server to crash
with an Out-of-Memory Error when bogus requests are sent.
> This reproduces when a very large request size is sent in the request header, making
the thrift server to allocate a large memory segment leading to OOM.
> LoadBalancer health checks are the first "candidate" for bogus requests
> Thrift developers admit this is a known issue with TBinaryProtocol and their recommandation
is to use TCompactProtocol/TFramedTransport but this requires all thrift clients to be updated
(might not be feasible atm)
> So we need a fix similar to CASSANDRA-475.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message