Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # dev >> RE: Suspected memory leak


Copy link to this message
-
Re: Suspected memory leak
Stack,
4633's summary and the workaround dont go together.
There is a rpc timeout related chatter (I am guilty) in 4633 which
might confuse reader joining the party late.

On Mon, Dec 5, 2011 at 12:03 PM, Stack <[EMAIL PROTECTED]> wrote:
> 2011/12/5 Ted Yu <[EMAIL PROTECTED]>:
>> Lars:
>> What you proposed below should be close to what netty does.
>> Instead of managing the complexity of NIO related code, we can delegate to
>> netty as what asynchbase does.
>> This discussion should be under a different thread / JIRA.
>>
>> sendParam() is called by HBaseClient.call() which is called by
>> WritableRpcEngine and SecureRpcEngine.
>> Can you elaborate on what you think the call hierarchy should be ?
>>
>> Overall, I think we can resolve HBASE-4633 and put further discussion under
>> https://issues.apache.org/jira/browse/HBASE-4956
>>
>
> We need the workaround though, don't we Ted?  We could commit the
> workaround as part of hbase-4633? (Thanks for opening hbase-4956)
>
> St.Ack
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB