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

ASF GitHub Bot commented on TRAFODION-2015:
-------------------------------------------

GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/502

    [TRAFODION-2015] hive/TEST018 fails in daily build regressions

    SequenceFileWriter java objects had global references on the JNI side.
    These references were not deleted because the corresponding JNI objects
    were not deallocated. This was causing the java objects leak.

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

    $ git pull https://github.com/selvaganesang/incubator-trafodion 
hive_test018_fail

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

    https://github.com/apache/incubator-trafodion/pull/502.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 #502
    
----
commit 87048757c954ce62d9384cf269944a48b2516dea
Author: selvaganesang <selva.govindara...@esgyn.com>
Date:   2016-05-25T22:09:15Z

    [TRAFODION-2015] hive/TEST018 fails in daily build regressions
    
    SequenceFileWriter java objects had global references on the JNI side.
    These references were not deleted because the corresponding JNI objects
    were not deallocated.

----


> hive/TEST018 fails in daily build regressions 
> ----------------------------------------------
>
>                 Key: TRAFODION-2015
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2015
>             Project: Apache Trafodion
>          Issue Type: Bug
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>
> It looks like CDH hive tests are failing both in Release 2.0 and master 
> because of java objects heap size is getting filled up. I suspect that 
> SequenceFileWriter  objects are getting leaked. New tests added to could have 
> triggered the java objects heap memory to be filled up.



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

Reply via email to