Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 0/2] swim broadcast
Date: Thu, 11 Apr 2019 01:13:26 +0300	[thread overview]
Message-ID: <9a34c777-f68e-402b-ae05-6aa35216ea9d@tarantool.org> (raw)
In-Reply-To: <6b91c5b7-2442-8ab7-22bd-414738f8e1d6@tarantool.org>



On 10/04/2019 21:13, Vladislav Shpilevoy wrote:
> 
> 
> On 10/04/2019 21:11, Konstantin Osipov wrote:
>> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/04/10 21:01]:
>>> The patchset introduces broadcast tasks and API to broadcast pings. A ping
>>> broadcast is useful when a cluster is just started, but UUIDs and URIs aren't
>>> known in advance.
>>
>> Why do you need to send a broadcast message across multiple
>> interfaces? Why not demand an interface name in the api?
> 
> No concrete reason. I just used the same strategy as
> gitlab.com/tarantool/membership. They broadcast on all
> interfaces.

If you want me to implement this feature, then confirm that,
please. It does not look hard to implement. Also in such a
case I would propose to make this argument optional.

Otherwise we could postpone the interface specification until
a specific request for that.

You need to choose.

> 
>>
>> -- 
>> Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
>> http://tarantool.io - www.twitter.com/kostja_osipov
>>
> 

      reply	other threads:[~2019-04-10 22:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 17:45 [tarantool-patches] " Vladislav Shpilevoy
2019-04-10 17:45 ` [tarantool-patches] [PATCH 1/2] swim: introduce broadcast tasks Vladislav Shpilevoy
2019-04-11 12:57   ` [tarantool-patches] " Konstantin Osipov
2019-04-11 13:46     ` Vladislav Shpilevoy
2019-04-10 17:45 ` [tarantool-patches] [PATCH 2/2] swim: expose ping broadcast API Vladislav Shpilevoy
2019-04-11 13:00   ` [tarantool-patches] " Konstantin Osipov
2019-04-11 13:00     ` Konstantin Osipov
2019-04-11 13:47     ` Vladislav Shpilevoy
2019-04-10 18:11 ` [tarantool-patches] Re: [PATCH 0/2] swim broadcast Konstantin Osipov
2019-04-10 18:13   ` Vladislav Shpilevoy
2019-04-10 22:13     ` Vladislav Shpilevoy [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=9a34c777-f68e-402b-ae05-6aa35216ea9d@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 0/2] swim broadcast' \
    /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