[
https://issues.apache.org/jira/browse/HBASE-24167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081187#comment-17081187
]
Hudson commented on HBASE-24167:
--------------------------------
Results for branch branch-2
[build #2598 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2598/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2598/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2598/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2598/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2598/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> [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
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> 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)