[
https://issues.apache.org/jira/browse/IGNITE-9492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617632#comment-16617632
]
ASF GitHub Bot commented on IGNITE-9492:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4773
IGNITE-9492 Ignore SingleMessage updated where there is in-progress exchange
…rogress.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9492
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4773.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4773
----
commit 0d0a25364eb4dfa97f57e98fa56e1e996476c604
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-09-17T14:46:45Z
IGNITE-9492 Ignore SingleMessage updated where there is exchange in
progress.
----
> 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)
