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] [Commented] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible
Date Tue, 30 Oct 2018 09:11:00 GMT

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

Alexey Goncharuk commented on IGNITE-9558:

[~ilantukh], we've got a performance drop of 3-4% on atomic-put benchmark. We need to investigate
and check if this can be fixed, then re-run a more thorough set of benchmarks.

> Avoid changing AffinityTopologyVersion on client connect when possible
> ----------------------------------------------------------------------
>                 Key: IGNITE-9558
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9558
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Alexey Goncharuk
>            Assignee: Ilya Lantukh
>            Priority: Major
>             Fix For: 2.8
> Currently a client join event changes discovery topology version which, in turn, changes
> When a client maps transaction on new AffinityTopologyVersion, corresponding message
is not processed on remote node until remote node receives the corresponding discovery event.
If discovery event delivery is delayed for some reason, this will result in transaction stalls
on client joins.
> Since the client node does not change partition affinity, we can safely map transactions
on the previous topology version and do not change the affinity topology version at all.
> Some cases need special care and probably do not qualify for this optimization, such
as when client has near cache or client hosts partition for REPLICATED cache.

This message was sent by Atlassian JIRA

View raw message