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 2016/11/16 07:53:59 UTC

[jira] [Updated] (IGNITE-3905) Optimize RendezvousAffinityFunction

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

Alexei Scherbakov updated IGNITE-3905:
--------------------------------------
    Fix Version/s:     (was: 1.8)
                   2.0

> Optimize RendezvousAffinityFunction
> -----------------------------------
>
>                 Key: IGNITE-3905
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3905
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, community, general
>    Affects Versions: 1.6
>            Reporter: Alexei Scherbakov
>            Priority: Critical
>             Fix For: 2.0
>
>
> Currently RendezvousAffinityFunction.assignPartition generates a lot of garbage if called very often, on example in case of rebalancing a lot of caches.
> This causes excessive pressure on GC, which is not always fast enough to clear memory, producing long GC pauses leading to node segmentation.
> We should cache calculation of nodeHashBytes in node attribute or resort to more efficient node hash calculation.



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