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

Jonathan Hsieh commented on HBASE-14742:
----------------------------------------

is there a reason why some are not all sleeps weren't converted to wait for 
tune's?

Likely out of scope, but would it be better to have a tuning metrics and 
verified an increment there as opposed to just memsize changes?

> TestHeapMemoryManager is flakey
> -------------------------------
>
>                 Key: HBASE-14742
>                 URL: https://issues.apache.org/jira/browse/HBASE-14742
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: HBASE-14742.patch
>
>
> On our internal build system we've seen TestHeapMemoryManager fail twice.
> {code}
> Failed tests: 
>   
> TestHeapMemoryManager.testWhenClusterIsReadHeavy:174->assertHeapSpaceDelta:317
>  null
>   
> TestHeapMemoryManager.testWhenClusterIsWriteHeavy:136->assertHeapSpaceDelta:317
>  null
> {code}



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

Reply via email to