You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/03/19 07:57:00 UTC
[jira] [Commented] (IGNITE-11484) Get rid of
ForkJoinPool#commonPool usage for system critical tasks
[ https://issues.apache.org/jira/browse/IGNITE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795799#comment-16795799 ]
Ignite TC Bot commented on IGNITE-11484:
----------------------------------------
{panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=3344135]]
* ZookeeperDiscoverySpiTestSuite1: ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver2 - 0,0% fails in last 395 master runs.
{color:#d04437}Queries 1{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=3344189]]
* IgniteBinaryCacheQueryTestSuite: DynamicIndexClientBasicSelfTest.testCreateIndexWithInlineSizeReplicatedAtomic - 0,0% fails in last 395 master runs.
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3344213&buildTypeId=IgniteTests24Java8_RunAll]
> Get rid of ForkJoinPool#commonPool usage for system critical tasks
> ------------------------------------------------------------------
>
> Key: IGNITE-11484
> URL: https://issues.apache.org/jira/browse/IGNITE-11484
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Rakov
> Assignee: Ivan Rakov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We use ForkJoinPool#commonPool for sorting checkpoint pages.
> This may backfire if common pool is already utilized in current JVM: checkpoint may wait for sorting for a long time, which in turn will cause user load dropdown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)