[jira] [Resolved] (HBASE-24167) [Flakey Tests] TestHRegionWithInMemoryFlush#testWritesWhileScanning gets stuck MVCC

["Michael Stack (Jira)" <ji...@apache.org>]

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

Michael Stack resolved HBASE-24167.
-----------------------------------
    Fix Version/s: 2.2.5
         Assignee: Michael Stack
       Resolution: Fixed

Helps w/ test flakyness. There is probably issue in here when in-memory compaction enabled but have not dug in. 

> [Flakey Tests] TestHRegionWithInMemoryFlush#testWritesWhileScanning gets stuck MVCC
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-24167
>                 URL: https://issues.apache.org/jira/browse/HBASE-24167
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.2.5
>
>         Attachments: 0001-HBASE-24167-Flakey-Tests-TestHRegionWithInMemoryFlus.patch
>
>
> I see this in recent nightly fails on branch-2, my experimental branch. It happened in the two builds last night. It was only test to fail. Both failed with:
>  2020-04-10 07:42:46,700 WARN  [Time-limited test] regionserver.MultiVersionConcurrencyControl(228): STUCK: MultiVersionConcurrencyControl{readPoint=8684,              writePoint=8686}
> I ran the test in my  harness and it pushes up against heap limits for sure, especially after recent cut down in forked jvm size.
> For now, see if alleviating scope of testWritesWhileScanning just when called from this test helps w/ flakeyness. Probably worth a deep dive why we get into this state w/ in-memory compaction.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)