From: Kirill Yukhin <kyukhin@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>, kostja@tarantool.org
Subject: Re: [tarantool-patches] Re: [PATCH 1/1] Allow to ignore space formats via command line option
Date: Tue, 7 Aug 2018 21:09:50 +0300 [thread overview]
Message-ID: <20180807180950.vexkeuhfaf7dbwyu@tarantool.org> (raw)
In-Reply-To: <17a2a616-2e8a-7b2c-0500-78fabbee64d4@tarantool.org>
Hello Vlad,
On 03 авг 16:58, Vladislav Shpilevoy wrote:
> On 03/08/2018 16:47, Vladimir Davydov wrote:
> > On Fri, Aug 03, 2018 at 03:46:26PM +0300, Vladislav Shpilevoy wrote:
> > > It is a common case that an instance is running on a version
> > > 1.6.*, then is upgraded to 1.9 with box.schema.upgrade(). But
> > > some of users has malformed space formats, and some of them got
> > > and ignored errors on box.schema.upgrade(). Such half-upgraded
> > > data can not be used to start a new version due to format
> > > violations, and can not be rolled back because some of new system
> > > spaces managed to be created. And we can not repair raw xlogs and
> > > snapshots because we have no such tools and they are zipped.
> > >
> > > So it would be useful to have a command line option
> > > --ignore-space-formats. It would allow to start an instance on
> > > the spaces with malformed formats, fix them, create a snapshot
> > > and then start with the formats turned on.
> > >
> > > Closes #3605
> > >
> > > @TarantoolBot document
> > > Title: Command line option '--ignore-space-formats'
> > > The option allows to turn off space formats validation before
> > > the instance is started. Usefull to fix malformed formats after
> > > an upgrade from version < 1.7.5 to >= 1.7.5.
> >
> > Why a command line option? Why not a box.cfg parameter?
> > Or, even better, box.cfg.force_recovery?
> >
>
> I just do not want to clog box.cfg options with this
> pure debug one. Force_recovery should skip violating
> records instead of ignoring the format. But I don't
> mind, for me all the 3 ways are ok and helps me to
> repair customers with broken schemes. So if you want,
> I can add a box.cfg option or reuse force_recovery
> to always ignore space formats. What should I do?
I think adding box.cfg{} parameter is more flexible approach.
You can start w/ such option turned ON, and the turn it OFF
w/o restart of whole instance.
--
Regards, Kirill Yukhin
prev parent reply other threads:[~2018-08-07 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 12:46 [tarantool-patches] " Vladislav Shpilevoy
2018-08-03 13:47 ` Vladimir Davydov
2018-08-03 13:58 ` [tarantool-patches] " Vladislav Shpilevoy
2018-08-07 18:09 ` Kirill Yukhin [this message]
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=20180807180950.vexkeuhfaf7dbwyu@tarantool.org \
--to=kyukhin@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=vdavydov.dev@gmail.com \
--subject='Re: [tarantool-patches] Re: [PATCH 1/1] Allow to ignore space formats via command line option' \
/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