ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-2834) IGFS: Introduce optional co-location of metadata.
Date Thu, 17 Mar 2016 14:02:33 GMT

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

Vladimir Ozerov reassigned IGNITE-2834:
---------------------------------------

    Assignee: Vladimir Ozerov

> 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)

Mime
View raw message