You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Phabricator (Updated) (JIRA)" <ji...@apache.org> on 2012/03/10 02:42:59 UTC
[jira] [Updated] (HBASE-5560) Avoid RegionServer GC caused by
timed-out calls
[ https://issues.apache.org/jira/browse/HBASE-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phabricator updated HBASE-5560:
-------------------------------
Attachment: D2241.1.patch
dhruba requested code review of "[jira][HBASE-5560] Avoid RegionServer GC caused by timed-out calls".
Reviewers: stack, tedyu, sc, JIRA
A slow client is not consuming rpc responses from the client. But the server caches the call responses uptil 15 minutes (hardcoded). This caused the regionserver to run out of old-gen and trigger a full GC.
This patch makes the 15 minute value to be settable by a configurable parameter "ipc.client.call.purge.timeout". The default is still 15 minutes to maintain backward compatibility.
TEST PLAN
Run all unit tests
REVISION DETAIL
https://reviews.facebook.net/D2241
AFFECTED FILES
src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/4923/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
> Avoid RegionServer GC caused by timed-out calls
> -----------------------------------------------
>
> Key: HBASE-5560
> URL: https://issues.apache.org/jira/browse/HBASE-5560
> Project: HBase
> Issue Type: Improvement
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: D2241.1.patch
>
>
> The HBaseRpcServer queues up rpc responses if the socket connection to the client is not yet ready to receive data. Calls are queued here until a 15 minute timeout occurs. I am able to generate a full GC when I artificially make a client read rpc-responses very slowly. This jira is to make this 15 minute time configurable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira