From: Konstantin Osipov <kostja@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v2 3/3] swim: introduce suspicion
Date: Thu, 25 Apr 2019 13:44:47 +0300 [thread overview]
Message-ID: <20190425104447.GH29257@atlas> (raw)
In-Reply-To: <d4d4d9fedd0320fc2919dfff51880129ee91b8ac.1556137229.git.v.shpilevoy@tarantool.org>
* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/04/25 00:46]:
> Suspicion component is a way how SWIM protects from
> false-positive failure detections. When the network is slow, or
> a SWIM node does not manage to process messages in time because
> of being overloaded, other nodes will not receive ACKs in time,
> but it is too soon to declare the member dead.
>
> The nodes will mark the member as suspected, and will ping it
> indirectly, via other members. It 1) gives the suspected member
> more time to respond on ACKs, 2) protects from the case when it
> is a network problem on particular channels.
>
> Part of #3234
OK to push.
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2019-04-25 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 20:21 [tarantool-patches] [PATCH v2 0/3] swim suspicion Vladislav Shpilevoy
2019-04-24 20:21 ` [tarantool-patches] [PATCH v2 1/3] swim: store sender UUID in swim io tasks Vladislav Shpilevoy
2019-04-25 10:31 ` [tarantool-patches] " Konstantin Osipov
2019-04-24 20:21 ` [tarantool-patches] [PATCH v2 2/3] swim: introduce routing Vladislav Shpilevoy
2019-04-25 10:43 ` [tarantool-patches] " Konstantin Osipov
2019-04-25 13:50 ` Vladislav Shpilevoy
2019-04-25 13:55 ` Konstantin Osipov
2019-04-24 20:22 ` [tarantool-patches] [PATCH v2 3/3] swim: introduce suspicion Vladislav Shpilevoy
2019-04-25 10:44 ` Konstantin Osipov [this message]
2019-04-25 13:50 ` [tarantool-patches] Re: [PATCH v2 0/3] swim suspicion 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=20190425104447.GH29257@atlas \
--to=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH v2 3/3] swim: introduce suspicion' \
/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