You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Kondakov (JIRA)" <ji...@apache.org> on 2018/03/26 15:11:00 UTC
[jira] [Assigned] (IGNITE-7806) SQL TX: Backup update protocol
[ https://issues.apache.org/jira/browse/IGNITE-7806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Kondakov reassigned IGNITE-7806:
--------------------------------------
Assignee: Roman Kondakov
> SQL TX: Backup update protocol
> ------------------------------
>
> Key: IGNITE-7806
> URL: https://issues.apache.org/jira/browse/IGNITE-7806
> Project: Ignite
> Issue Type: Task
> Components: cache, sql
> Reporter: Vladimir Ozerov
> Assignee: Roman Kondakov
> Priority: Major
>
> Currently TX SQL protocol works as follows:
> 1) Lock request is sent to {{PRIMARY}} node where updates are applied immediately.
> 2) Updated values are stored in-memory
> 3) When commit command is issued, updates are propagated to {{BACKUP}}s.
> This requires data to be stored in memory at some point. We should design better protocol which will allow for updates to be propagated to backups efficiently.
> Ticket is related (or may be even duplicates) to IGNITE-7186.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)