You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Suresh Subbiah (JIRA)" <ji...@apache.org> on 2016/05/16 16:57:12 UTC

[jira] [Assigned] (TRAFODION-1996) TLOG uses excessive memory when aging old entries

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

Suresh Subbiah reassigned TRAFODION-1996:
-----------------------------------------

    Assignee: Sean Broeder

> TLOG uses excessive memory when aging old entries
> -------------------------------------------------
>
>                 Key: TRAFODION-1996
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1996
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: dtm
>    Affects Versions: 2.0-incubating
>            Reporter: Sean Broeder
>            Assignee: Sean Broeder
>             Fix For: 2.1-incubating
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> When deleting old entries in the TLOG tables a complete table scan is performed and a list of deletes is accumulated.  This was done to try to improve performance by attempting to delete all old entries in a single list of deletes.  However, with extremely large scans the list of deletes can become quite large and in a worst case scenario if a RS failure occurs due to a long GC we would need to scan the entire table again and possibly cause another RS failure due to a long GC pause.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)