ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-9492) Refactor processing SingleMessage with exchangeId==null
Date Wed, 26 Sep 2018 11:48:00 GMT

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

Alexey Goncharuk updated IGNITE-9492:
-------------------------------------
    Ignite Flags:   (was: Docs Required)

> 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.
> We shouldn't create a big SingleMessages for each of partition state change and use more
shrinked/tiny messages for that.



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

Mime
View raw message