You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/18 15:09:33 UTC
[jira] [Closed] (IGNITE-2834) IGFS: Introduce optional co-location
of metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov closed IGNITE-2834.
-----------------------------------
> IGFS: Introduce optional co-location of metadata.
> -------------------------------------------------
>
> Key: IGNITE-2834
> URL: https://issues.apache.org/jira/browse/IGNITE-2834
> Project: Ignite
> Issue Type: Task
> Components: IGFS
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> *Description*
> IGFS meta manager heavily relies on transactions in REPLICATED cache. Some transactions operate on more than 1 keys. As key affinity is not specified at the moment, different Ignite nodes host different primary keys. As a result, transaction on multiple keys might lead to relatively big number of network requests during 2PC.
> *Solution*
> If we co-located all metadata on a single node, transaction commit will require less network trips, thus decreasing latency and contention.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)