You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2018/09/10 09:27:00 UTC

[jira] [Updated] (IGNITE-9492) Refactor processing SingleMessage with exchangeId==null

     [ https://issues.apache.org/jira/browse/IGNITE-9492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Kovalenko updated IGNITE-9492:
------------------------------------
    Summary: Refactor processing SingleMessage with exchangeId==null  (was: Limit number of threads which process SingleMessage with exchangeId==null)

> Refactor processing SingleMessage with exchangeId==null
> -------------------------------------------------------
>
>                 Key: IGNITE-9492
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9492
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 2.5
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>            Priority: Major
>             Fix For: 2.7
>
>
> Currently, after each PME coordinator spend a lot of time on processing correcting Single messages (with exchange id == null). This leads to growing inbound/outbound messages queue and delaying other coordinator-aware processes.
> Processing single messages with exchange id == null are not so important to give all available resources to it. We should limit the number of sys-threads which are able to process such single messages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)