From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 6A385307B7 for ; Thu, 20 Jun 2019 06:34:10 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blB2vdNQgocC for ; Thu, 20 Jun 2019 06:34:10 -0400 (EDT) Received: from smtp57.i.mail.ru (smtp57.i.mail.ru [217.69.128.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id AC985307AD for ; Thu, 20 Jun 2019 06:34:09 -0400 (EDT) From: =?utf-8?B?0JPQtdC+0YDQs9C40Lkg0JrQuNGA0LjRh9C10L3QutC+?= Subject: [tarantool-patches] Re: [PATCH] ddl: No replication for temp and local spaces Date: Thu, 20 Jun 2019 13:34:00 +0300 Message-ID: <3949285.zUfRBHxran@home.lan> In-Reply-To: <20190620090038.GA18958@atlas> References: <20190619124823.7021-1-szudin@tarantool.org> <20190620090038.GA18958@atlas> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7659391.uc94g7UbQx"; micalg="pgp-sha256"; protocol="application/pgp-signature" Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: tarantool-patches@freelists.org Cc: Konstantin Osipov , Stanislav Zudin --nextPart7659391.uc94g7UbQx Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Thursday, June 20, 2019 12:00:38 PM MSK Konstantin Osipov wrote: > * Stanislav Zudin [19/06/19 15:53]: > > Do not spread the space:truncate() to replicas if the > > affected space is local and temporary. > > While I agree with Georgy's comment that when it comes to > TEMPORARY spaces, we should replicate all DDL but TRUNCATE, for > node-local spaces I think nothing should be replicated. This is > the idea of node-local spaces to begin with. It breaks backward compatibility and inconsistent all. I'm pretty sure we definitely should replicate all local space schema changes because it is only possible way to keep a fallback possible. In the opposite case we were in duty to keep all local spaces definition in mind and apply them before replica became master. The other solution is to populate local space changes across whole cluster by hands instead of replication and it looks as ugly as previous one. --nextPart7659391.uc94g7UbQx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEFB+nbqWGnp59Rk9ZFSyY70x8X3sFAl0LYRgACgkQFSyY70x8 X3uxWgf/Y4ZsxSB7qImxvqmfIlRU56ze1LnM8EevolVNnyHkej31FoJ2MPsFFEEf DhQ6080FHd8sStX/u/7h6CuvH/7FIc/+RjXhCdjot6+7HIuUpDJBWSLjq/4rwrtt CqgmH4P5q0lKVCAO3RFa7St9x0NZLEjuFT2qg/mTdFfcBOLXDnrkf1oy/9P8R1BG /TDPl9VO0VAxjZ7NmnYbPeRSjWCY7gR6nmE0W5sxlMWCRv0clVQIM1U1HkXCCPA/ HJRpEsQTsafwGnULQAi9r//dyCf3bim0MzyD1FpQ2Rml37idkl0mxU6sGw6E5UWE LlQh0KJPxjN/adKegDls7o25zGqrBA== =M7Pt -----END PGP SIGNATURE----- --nextPart7659391.uc94g7UbQx--