You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2013/09/16 11:03:54 UTC

[jira] [Updated] (TAJO-183) Creating too many TableMetaProto objects might lead a potential memory leak

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

Jihoon Son updated TAJO-183:
----------------------------

    Attachment: TAJO-183.patch

In this patch, TableMeta is changed to maintain values in local or proto as in the previous version of TableMeta.
Furthermore, I added the mergeProtoToLocal() function for the json conversion.
                
> Creating too many TableMetaProto objects might lead a potential memory leak
> ---------------------------------------------------------------------------
>
>                 Key: TAJO-183
>                 URL: https://issues.apache.org/jira/browse/TAJO-183
>             Project: Tajo
>          Issue Type: Improvement
>          Components: storage
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>             Fix For: 0.2-incubating
>
>         Attachments: TAJO-183.patch
>
>
> In the current TableMetaImpl, a pb object is created for every getProto() calls.
> Since TableMeta.getProto() is called for creating a Fragment, the current implementation shall cause an out of memory exception when too many pb objects are created for a large data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira