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 2/2] fiber: destroy fiber.storage created by iproto
Date: Tue, 10 Dec 2019 11:21:02 +0300 [thread overview]
Message-ID: <20191210082102.GC21413@atlas> (raw)
In-Reply-To: <a8929b96-d644-df4f-7a2b-85f28f254d8c@tarantool.org>
* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/12/10 10:22]:
> > The danger of reporting, self-assigning and fixing a bug is that
> > ... it might be not a bug.
>
> I agree. Except when something is obviously a bug which is
> clearly the case.
>
> >
> > Users should know that iproto fibers are pooled, not
> > created/destroyed on demand. So fiber local storage is simply not
> > making any sense for them.
>
> Here I disagree. Users should not know anything about whether
> the fibers are pooled, when, and how.
>
> If so, then please, give an example, when such a strange
> fiber.storage is needed? I just really can't come up with a
> usage case.
>
> I did a public poll to understand what a behaviour is expected,
> and not a single person expects, that pooled vs not pooled fiber
> would affect its behaviour. Pool is like a cache. It should not
> be visible. You literally said it in another thread about SQL
> PREPARE.
You had a discussion with the community on the channel and many
people favour your fix. This is how you handle this!
I will send a review.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-12-10 8:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 19:28 [Tarantool-patches] [PATCH 0/2] Fiber storage leak Vladislav Shpilevoy
2019-12-08 19:28 ` [Tarantool-patches] [PATCH 1/2] fiber: unref fiber.storage via global Lua state Vladislav Shpilevoy
2019-12-11 23:57 ` Igor Munkin
2019-12-12 8:50 ` Konstantin Osipov
2019-12-12 23:38 ` Vladislav Shpilevoy
2019-12-13 10:44 ` Igor Munkin
2019-12-08 19:28 ` [Tarantool-patches] [PATCH 2/2] fiber: destroy fiber.storage created by iproto Vladislav Shpilevoy
2019-12-09 7:21 ` Konstantin Osipov
2019-12-09 23:31 ` Vladislav Shpilevoy
2019-12-10 8:21 ` Konstantin Osipov [this message]
2019-12-10 8:32 ` Konstantin Osipov
2019-12-10 22:59 ` Vladislav Shpilevoy
2019-12-11 7:08 ` Konstantin Osipov
2019-12-11 21:23 ` Vladislav Shpilevoy
2019-12-12 0:00 ` Igor Munkin
2019-12-12 23:37 ` Vladislav Shpilevoy
2019-12-13 13:35 ` Igor Munkin
2019-12-12 8:46 ` Konstantin Osipov
2019-12-13 0:02 ` Vladislav Shpilevoy
2019-12-13 7:58 ` Konstantin Osipov
2019-12-13 23:11 ` Vladislav Shpilevoy
2019-12-14 12:26 ` Konstantin Osipov
2019-12-14 12:30 ` Konstantin Osipov
2019-12-14 12:33 ` Konstantin Osipov
2019-12-14 16:49 ` Vladislav Shpilevoy
2019-12-14 20:59 ` Vladislav Shpilevoy
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=20191210082102.GC21413@atlas \
--to=kostja.osipov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 2/2] fiber: destroy fiber.storage created by iproto' \
/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