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 2022/04/12 20:54:00 UTC

[jira] [Commented] (IGNITE-16827) Added new Ignite system property that allows to reduce a number diagnostic messages.

    [ https://issues.apache.org/jira/browse/IGNITE-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521333#comment-17521333 ] 

Ignite TC Bot commented on IGNITE-16827:
----------------------------------------

{panel:title=Branch: [pull/9958/head] Base: [master] : Possible Blockers (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Scala (Examples){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6518850]]

{panel}
{panel:title=Branch: [pull/9958/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Basic 4{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6518861]]
* {color:#013220}IgniteBasicTestSuite2: IgniteDiagnosticPartitionReleaseFutureLimitTest.testDiagnosticMessageLimit - PASSED{color}

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6518880&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Added new Ignite system property that allows to reduce a number diagnostic messages.
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-16827
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16827
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vyacheslav Koptilin
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Additional diagnostic messages that have been added under IGNITE-5155 and IGNITE-5774 (at least) can produce a huge string objects.
> For example, CacheObjectsReleaseFuture can include thousands futures, and therefore this lead to extreme stress on GC and takes a significant time. Moreover, it may lead to thread pool starvation on sys pool:
> {noformat}
> 00:15:48.807 ^-- System thread pool [active=8, idle=0, qSize=52]
> ...
> 00:22:49.429 ^-- System thread pool [active=8, idle=0, qSize=346]
> ...
> 07:09:30.306 ^-- System thread pool [active=8, idle=0, qSize=18515]
> ...
> 09:52:42.118 ^-- System thread pool [active=8, idle=0, qSize=26365]
> {noformat}
> {noformat}
> 00:15:18.821 WARN  Possible thread pool starvation detected (no task completed in last 30000ms, is system thread pool size large enough?)
> ...
> 06:31:14.114 WARN  Possible thread pool starvation detected (no task completed in last 30000ms, is system thread pool size large enough?)
> ...
> 09:51:49.455 WARN  Possible thread pool starvation detected (no task completed in last 30000ms, is system thread pool size large enough?)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)