Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/1] wal: simplify rollback
Date: Sun, 3 May 2020 13:46:29 +0300	[thread overview]
Message-ID: <20200503104629.GD23133@atlas> (raw)
In-Reply-To: <e09e2aca2559cfa8c02d832ea357b9e2e9c7a3b0.1588286902.git.v.shpilevoy@tarantool.org>

* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [20/05/01 22:16]:

This isn't a particularly bad patch. It changes one fairly trivial
implementation to another. You claim it simplifies the rollback, I
believe it makes it more convoluted with the rest of the code. 

In any case it's a matter of taste - so perhaps your taste is
better than mine.

But the reason you had to do this patch *only* because you want to manage
rollback in tx - as you claim yourself here:

> 
> Also there is now a single route for commit and rollback cbus
> messages, called tx_complete_batch(). This change will come in
> hand in scope of synchronous replication, when WAL write won't be
> enough for commit. And therefore 'commit' as a concept should be
> washed away from WAL's code gradually. Migrate to solely txn
> module.

The reason it has to be managed in TX is that you don't want to
build synchronous replication on top of in-memory relay, which
would allow you to manage RAFT rollback in WAL.

When I called you out on the fact that you can't simply build your
implementation on top of existing code without an in-memory relay,
and it will require a bunch of hacks you got mad at me.

Now what? You will ask Nikita to review this and Kirill will
"LGTM" it and you will proceed with your own design - and even may
release it as a "stable" version over some time.

This "stable version may be even useful to some people. 

Will it be worth a dime on a worldwide scale? No.

-- 
Konstantin Osipov, Moscow, Russia

  reply	other threads:[~2020-05-03 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 22:50 Vladislav Shpilevoy
2020-05-03 10:46 ` Konstantin Osipov [this message]
2020-05-03 16:45   ` Vladislav Shpilevoy
2020-05-03 19:30     ` Konstantin Osipov
2020-05-06  7:55 ` Cyrill Gorcunov
2020-05-06 15:38 ` Sergey Ostanevich
2020-05-06 21:43   ` Vladislav Shpilevoy
2020-05-07 10:28     ` Sergey Ostanevich
2020-05-07 21:37       ` Vladislav Shpilevoy
2020-05-08  8:12 ` Kirill Yukhin

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=20200503104629.GD23133@atlas \
    --to=kostja.osipov@gmail.com \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 1/1] wal: simplify rollback' \
    /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