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

Posted to issues@ignite.apache.org by "Alexei Scherbakov (JIRA)" <ji...@apache.org> on 2019/01/16 13:50:00 UTC

[jira] [Resolved] (IGNITE-9926) Improve metada distribution speed in a scenario with concurrent updates for the same schema

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

Alexei Scherbakov resolved IGNITE-9926.
---------------------------------------
    Resolution: Fixed

Fixed by IGNITE-10376

> Improve metada distribution speed in a scenario with concurrent updates for the same schema
> -------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-9926
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9926
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexei Scherbakov
>            Assignee: Sergey Antonov
>            Priority: Major
>             Fix For: 2.8
>
>
> If multiple threads start putting same object with non-existent schema in the cache simultaneously every update will trigger full propose-accept round trip in current implementation.
> Propose message should be send only for first update, others should wait for it's completion instead of sending messages for same schema.



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