hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19715) Fix timing out test TestMultiRespectsLimits
Date Sun, 07 Jan 2018 08:14:00 GMT

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

Chia-Ping Tsai updated HBASE-19715:
    Attachment: HBASE-19715.test.patch

The statistic is shown below. The patch add the loop to the #testMultiLimits for more statistic.

|| ||master||patch||
|elapsed time|81s|75s|
|total memory allocation|16.33GB|9.19GB|
|char array|7.29GB|1.08GB|

> Fix timing out test TestMultiRespectsLimits
> -------------------------------------------
>                 Key: HBASE-19715
>                 URL: https://issues.apache.org/jira/browse/HBASE-19715
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Appy
>            Assignee: Appy
>         Attachments: HBASE-19715.test.patch, failued.txt, passed.txt, screenshot-1.png,
screenshot-2.png, screenshot-3.png, screenshot-4.png
> !screenshot-1.png|width=800px!
> Attached logs for both cases, when it passes and fails.
> Link (temporary) to logs:
> passed:*view*/
> failed:*view*/
> Correlating across more runs, whenever the tests passes, it does so within 10-30sec of
3min deadline for medium tests.
> So i think we can make it pass by just increasing the timeout.
> But I'm a bit skeptical after seeing all those long GC pauses (10sec +) in the log. Test
code doesn't seem to be doing anything that intensive. Are we mismanaging the memory somewhere?

This message was sent by Atlassian JIRA

View raw message