[jira] [Commented] (HAWQ-200) Investigate AOSegfileStatus leak

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HAWQ-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035346#comment-15035346 ] 

ASF GitHub Bot commented on HAWQ-200:
-------------------------------------

GitHub user jianlirong opened a pull request:

    https://github.com/apache/incubator-hawq/pull/147

    HAWQ-200. Add the logic of freeing unused AO segment file status

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jianlirong/incubator-hawq HAWQ-200

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-hawq/pull/147.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #147
    
----
commit 3118ad8e4494dba025cdc744530767b4ac91e708
Author: Lirong Jian <ji...@gmail.com>
Date:   2015-12-02T06:08:18Z

    HAWQ-200. Add the logic of freeing unused AO segment file status

----


> Investigate AOSegfileStatus leak
> --------------------------------
>
>                 Key: HAWQ-200
>                 URL: https://issues.apache.org/jira/browse/HAWQ-200
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Storage
>            Reporter: Lirong Jian
>            Assignee: Lirong Jian
>
> It is usual to encounter the issue of "cannot open more than 262144 append-only table segment files concurrently", even sometimes the number of the open segment files in the underlying query is less than 262144.
> It is suspected that AOSegFileStatus might be leaked (not freed) in some circumstances.



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