From dev-return-31377-apmail-ignite-dev-archive=ignite.apache.org@ignite.apache.org Mon Feb 26 08:02:08 2018 Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0DD7818E94 for ; Mon, 26 Feb 2018 08:02:08 +0000 (UTC) Received: (qmail 73766 invoked by uid 500); 26 Feb 2018 08:02:07 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 73647 invoked by uid 500); 26 Feb 2018 08:02:07 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 73636 invoked by uid 99); 26 Feb 2018 08:02:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2018 08:02:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C993AC5EB0 for ; Mon, 26 Feb 2018 08:02:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id fp2EqkLIgPWI for ; Mon, 26 Feb 2018 08:02:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CB7605F1B9 for ; Mon, 26 Feb 2018 08:02:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D400DE0339 for ; Mon, 26 Feb 2018 08:02:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 26FD0240DE for ; Mon, 26 Feb 2018 08:02:00 +0000 (UTC) Date: Mon, 26 Feb 2018 08:02:00 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-7806) SQL TX: Backup update protocol MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Vladimir Ozerov created IGNITE-7806: --------------------------------------- Summary: 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 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)