You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2010/07/01 00:01:57 UTC

[jira] Created: (HBASE-2810) Profiling of ReplicationSource to determine if it's better to reuse lists or not

Profiling of ReplicationSource to determine if it's better to reuse lists or not
--------------------------------------------------------------------------------

                 Key: HBASE-2810
                 URL: https://issues.apache.org/jira/browse/HBASE-2810
             Project: HBase
          Issue Type: Task
            Reporter: Jean-Daniel Cryans
            Assignee: Jean-Daniel Cryans
             Fix For: 0.21.0


Following a discussion with Stack, the way ReplicationSource manages the list that holds all the entries read from a HLog may be going against GC instead of hand in hand with it. We need to profile the current way it's done VS creating new lists every time we tail.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (HBASE-2810) Profiling of ReplicationSource to determine if it's better to reuse lists or not

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/HBASE-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans resolved HBASE-2810.
---------------------------------------

    Resolution: Invalid

We've been running replication in production for a while, and memory isn't an issue more than usual.

> Profiling of ReplicationSource to determine if it's better to reuse lists or not
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-2810
>                 URL: https://issues.apache.org/jira/browse/HBASE-2810
>             Project: HBase
>          Issue Type: Task
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.90.0
>
>
> Following a discussion with Stack, the way ReplicationSource manages the list that holds all the entries read from a HLog may be going against GC instead of hand in hand with it. We need to profile the current way it's done VS creating new lists every time we tail.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.