From: Georgy Kirichenko <georgy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Serge Petrenko <sergepetrenko@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2] iproto: introduce a proxy module.
Date: Thu, 04 Oct 2018 14:54:27 +0300 [thread overview]
Message-ID: <2337967.721MrxTllO@home.lan> (raw)
In-Reply-To: <20181002180554.1142-1-sergepetrenko@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Hi and thank you for the patch! Overall it looks good but I have some
comments.
- I would like if you created a dedicated fiber pool and cbus endpoint to
perform IPROTO<->TX interconnection. In that case iproto and tx
initialization could be more clearly splitted.
- I think we could have only one hash table to locate a corresponding
connection with "username@uri" instead of two-level routing.
- It should be fine to introduce some error injections.
- If you allocate and free a lots of same space objects then mempool
is better option than (m/c)alloc/free
Also I have some comments inline.
> +
> + instance->is_ro = is_ro;
> + instance->is_local = is_local;
> + if (is_local) {
> + /* There can be only one local instance. */
> + assert(local_instance == NULL);
> + assert(box_is_configured());
This function works in the IPROTO thread and calling TX threaded function may
lead to undefined behavior.
> + local_instance = instance;
> + } else if (uri_parse(&instance->uri, uri) || !instance->uri.service) {
> + free(instance);
> + diag_set(ClientError, ER_CFG, "uri",
> + "expected host:service or /unix.socket");
> + return NULL;
> + }
> +
> + rlist_add_tail(&proxy_instances, &instance->link);
> +
> +
> + if (!is_proxy_configured) {
> + /*
> + * This can't throw, but should not be
> + * done in case of exception.
> + */
> +process_locally:
> + cpipe_push_input(&tx_pipe, &msg->base);
> + continue;
> + }
> +
> + struct proxy_instance *instance = proxy_find_instance(msg);
> + if (instance == NULL) {
I think some actions with request should be done, at least clearing an input
buffer space.
> + diag_log();
> + continue;
> + }
> + if (instance == local_instance) {
> + if (msg->header.type != IPROTO_AUTH)
> + goto process_locally;
> + struct proxy_auth_msg *m = (struct proxy_auth_msg
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-04 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 18:05 [tarantool-patches] " Serge Petrenko
2018-10-03 8:49 ` Vladimir Davydov
2018-10-04 11:54 ` Georgy Kirichenko [this message]
2018-10-08 10:44 ` Vladimir Davydov
2018-10-16 18:35 ` [tarantool-patches] " Konstantin Osipov
2018-10-08 16:48 ` [tarantool-patches] " Vladimir Davydov
2018-10-16 18:39 ` [tarantool-patches] " Konstantin Osipov
2018-10-17 8:35 ` Vladimir Davydov
2018-10-17 15:31 ` Konstantin Osipov
2018-10-08 19:45 ` [tarantool-patches] " Vladimir Davydov
2018-10-16 18:42 ` [tarantool-patches] " Konstantin Osipov
2018-10-23 17:26 ` 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=2337967.721MrxTllO@home.lan \
--to=georgy@tarantool.org \
--cc=sergepetrenko@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v2] iproto: introduce a proxy module.' \
/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