You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2016/12/15 09:17:58 UTC

[jira] [Updated] (IGNITE-4435) Discovery data distribution process optimization

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

Sergey Chugunov updated IGNITE-4435:
------------------------------------
    Fix Version/s: 2.0

> Discovery data distribution process optimization
> ------------------------------------------------
>
>                 Key: IGNITE-4435
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4435
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Sergey Chugunov
>             Fix For: 2.0
>
>
> h2. Notes
> Previously upon new node joining topology grid components on each node has been collecting discovery data independently from the same components on other nodes.
> This lead to a situation when *TcpDiscoveryNodeAddedMessage* and *TcpDiscoveryNodeAddFinishedMessage* carried a lot of duplicated data wasting network traffic.
> Refactoring done within [IGNITE-4157|https://issues.apache.org/jira/browse/IGNITE-4157] introduced a way to reduce duplication, but only *GridMarshallerMappingProcessor* component took advantage of it.
> h2. Acceptance Criteria
> *  Identify all components needed to be optimized in terms of discovery data collection.
> * Refactor them to reduce duplication of discovery data.
> * Remove *filterDuplicatedData* method as obsolete from *DiscoveryDataContainer* when refactoring is done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)