You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/18 10:51:18 UTC

[jira] [Commented] (HAWQ-420) Memory leaks in DataLocality during ANALYZE lasting 1 ~ 2 days on 100 nodes cluster.

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

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

GitHub user zhangh43 opened a pull request:

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

    HAWQ-420. Memory leaks in DataLocality during ANALYZE lasting 1 ~ 2 d…

    …ays on 100 nodes cluster.
    
    Just add TRY CATCH in calculate_planner_segment_num()

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

    $ git pull https://github.com/zhangh43/incubator-hawq hawq420

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

    https://github.com/apache/incubator-hawq/pull/353.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 #353
    
----
commit 87644161e0ecf7f4978b20dffb66530026136423
Author: hubertzhang <hz...@pivotal.io>
Date:   2016-02-18T09:31:19Z

    HAWQ-420. Memory leaks in DataLocality during ANALYZE lasting 1 ~ 2 days on 100 nodes cluster.

----


> Memory leaks in DataLocality during ANALYZE lasting 1 ~ 2 days on 100 nodes cluster.
> ------------------------------------------------------------------------------------
>
>                 Key: HAWQ-420
>                 URL: https://issues.apache.org/jira/browse/HAWQ-420
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Core
>            Reporter: Hubert Zhang
>            Assignee: Hubert Zhang
>
> On about 100 nodes cluster (SFO), we load data to lineitem and then do ANALYZE on it. It takes 1 ~ 2 days before we cancel the ANALYZE and the QD uses about 48G memory. The major memory consumers are:
> ```
> TopMemoryContext: 48G
> ----------------------------------------------------------
> other: 44G
> split_to_segment_mapping_context: 4G
> ```



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