You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Adrian Muraru (JIRA)" <ji...@apache.org> on 2014/06/06 23:52:02 UTC
[jira] [Commented] (HBASE-11052) Sending random data crashes thrift
service
[ https://issues.apache.org/jira/browse/HBASE-11052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020418#comment-14020418 ]
Adrian Muraru commented on HBASE-11052:
---------------------------------------
Patches updated based on [~apurtell] review
> 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_0.94_v2.patch, HBASE-11052_0.94_v3.patch, HBASE-11052_trunk_v1.patch, HBASE-11052_trunk_v2.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)