Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Георгий Кириченко" <georgy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] Do not enable commit if read_only = true
Date: Sun, 03 Mar 2019 23:49:46 +0300	[thread overview]
Message-ID: <1779552.GDyJA9gWEY@home.lan> (raw)
In-Reply-To: <20190228102530.GB18858@chai>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On Thursday, February 28, 2019 1:25:30 PM MSK Konstantin Osipov wrote:
> * Vladimir Davydov <vdavydov.dev@gmail.com> [19/02/27 12:26]:
> > On Wed, Feb 27, 2019 at 10:36:00AM +0300, Georgy Kirichenko wrote:
> > > Disable commit if server is in read only mode.
> > 
> > The commit message is very poor. Please elaborate why this is important.
> 
> Having thought about it we should go over all in-flight
> transactions in vinyl and abort them.
> 
> We already use this approach on DDL.
> We could make it more general.
I did a little investigation and found that current implementation does not 
allow us do reach expected behavior using vinyl aborts because of
* transaction placed in the write set only after uniqueness check - this leads 
to a race if read only was set during this check.
* it is valid only for vy_update and vy_upsert invocations.
* ddl could stuck at schema_latch and continues after read_only was set.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-03-03 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  7:36 [tarantool-patches] " Georgy Kirichenko
2019-02-27  9:02 ` Vladimir Davydov
2019-02-28 10:25   ` [tarantool-patches] " Konstantin Osipov
2019-03-03 20:49     ` Георгий Кириченко [this message]
2019-03-04  9:41       ` Konstantin Osipov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1779552.GDyJA9gWEY@home.lan \
    --to=georgy@tarantool.org \
    --cc=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH] Do not enable commit if read_only = true' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox