You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/03/15 17:00:00 UTC
[jira] [Comment Edited] (HBASE-26828) Increase the concurrency when running UTs in pre commit job
[ https://issues.apache.org/jira/browse/HBASE-26828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507057#comment-17507057 ]
Andrew Kyle Purtell edited comment on HBASE-26828 at 3/15/22, 4:59 PM:
-----------------------------------------------------------------------
This has been committed to branch-2.4. In order for the change log to be correct for 2.4.11RC1 I have to resolve this JIRA right now.
was (Author: apurtell):
This has been committed to branch-2.4. In order for the change log to be correct I have to resolve this JIRA now.
> Increase the concurrency when running UTs in pre commit job
> -----------------------------------------------------------
>
> Key: HBASE-26828
> URL: https://issues.apache.org/jira/browse/HBASE-26828
> Project: HBase
> Issue Type: Improvement
> Components: jenkins, test
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.11
>
>
> The default forkCount is 0.25C. We used to run on a 16 cores machine so the concurrency is 4, but now our build nodes are all 8 cores, so the concurrency is 2. The build time is way more slower than before.
> Since we only have 2 slots on the build node, I think it is OK to increase the forkCount to 0.5C. But I'm not sure whether we should change the default value in pom, or we just set it in the pre commit job.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)