[
https://issues.apache.org/jira/browse/HBASE-24158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079643#comment-17079643
]
Michael Stack commented on HBASE-24158:
---------------------------------------
Ok. Pushed below on branch-2. Lets see if helps.
{code}
commit 2d117963809929e9523e47e94b7e5faab7db8e1a (HEAD -> 2)
Author: stack <[email protected]>
Date: Thu Apr 9 11:03:22 2020 -0700
HBASE-24158 [Flakey Tests] TestAsyncTableGetMultiThreaded
diff --git
a/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncTableGetMultiThreaded.java
b/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncTableGetMultiThreaded.java
index 7c896957fa..ce6bc05ca0 100644
---
a/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncTableGetMultiThreaded.java
+++
b/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAsyncTableGetMultiThreaded.java
@@ -98,7 +98,7 @@ public class TestAsyncTableGetMultiThreaded {
TEST_UTIL.getConfiguration().set(CompactingMemStore.COMPACTING_MEMSTORE_TYPE_KEY,
String.valueOf(memoryCompaction));
- TEST_UTIL.startMiniCluster(5);
+ TEST_UTIL.startMiniCluster(3);
SPLIT_KEYS = new byte[8][];
for (int i = 111; i < 999; i += 111) {
SPLIT_KEYS[i / 111 - 1] = Bytes.toBytes(String.format("%03d", i));
@@ -134,7 +134,7 @@ public class TestAsyncTableGetMultiThreaded {
@Test
public void test() throws Exception {
LOG.info("====== Test started ======");
- int numThreads = 10;
+ int numThreads = 7;
AtomicBoolean stop = new AtomicBoolean(false);
ExecutorService executor =
Executors.newFixedThreadPool(numThreads,
Threads.newDaemonThreadFactory("TestAsyncGet-"));
{code}
> [Flakey Tests] TestAsyncTableGetMultiThreaded
> ---------------------------------------------
>
> Key: HBASE-24158
> URL: https://issues.apache.org/jira/browse/HBASE-24158
> Project: HBase
> Issue Type: Bug
> Reporter: Michael Stack
> Priority: Major
> Attachments:
> 0001-HBASE-24158-Flakey-Tests-TestAsyncTableGetMultiThrea.patch
>
>
> I've already cut down the number of threads used by this test but it failed
> in nightly last night unable to close out its xml and locally it failed too
> in a run overnight. I ran it under harness and it seems well-behaved. It
> doesn't use much memory -- 700MB -- and thread counts are usual (~450). It
> does use near 100% CPU which is a little unusual. Otherwise, looks fine.
> Let me keep an eye on it. Could down the thread count more and use less
> processes... this makes it use less CPU. There does seems a bunch of overlap
> with tests done elsewhere.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
