Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alex Khatskevich <avkhatskevich@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>,
	tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 2/2] Fix discovery/reconfigure race
Date: Mon, 25 Jun 2018 15:48:24 +0300	[thread overview]
Message-ID: <f6e438ae-64af-7cb5-bf99-938e821f21c8@tarantool.org> (raw)
In-Reply-To: <edbc3f57-83b9-8434-7893-99857cacb699@tarantool.org>


>> +--
>> +-- Check route_map is not filled with old replica objects after
>> +-- recpnfigure.
>
> 1. Typo.
fixed
>
>>
>> +-- Simulate long `callro`.
>> +-- Stuck on first rs in replicasets.
>> +vshard.router.internal.errinj.LONG_DISCOVERY = true;
>
> 2. I do not see this error injection in the M.errinj
> declaration.
Fixed
+Renamed to ERRINJ_LONG_DISCOVERY
>
>> +---
>> +...
>> +for _, __ in pairs(vshard.router.internal.replicasets) do
>> +    vshard.router.discovery_wakeup()
>> +    fiber.sleep(0.02)
>> +end;
>
> 3. This cycle makes no sense. With set LONG_DISCOVERY it is
> equivalent to calling router.discovery_wakeup() once.
Disagree.
I need to stuck on the first routemap element. However I need to wakeup 
it #replicasets
times, because the discovery_fiber sleeps after each iteration.
>
>> +---
>> +...
>> +vshard.router.cfg(cfg);
>> +---
>> +...
>> +vshard.router.internal.errinj.LONG_DISCOVERY = nil;
>> +---
>> +...
>> +-- Do discovery iteration.
>> +vshard.router.discovery_wakeup()
>> +fiber.sleep(0.02)
>
> 4. Concrete timeouts are the way to create an unstable test.
> Please, get rid of them and replace with 'while not cond do wait end'
> where necessary.
It is important that discovery fiber did only one iteration of 
discovery. So, If I want some `while` mechanism I want to introduce 
several synchronization and block/unblock phases.
I get you point and suggest compromise here.
1. I have places an assert here, which checks that expected discovery 
has occurred.
2. I have launched the test 100 times and it did not fail
>
>>   - true
>> diff --git a/vshard/router/init.lua b/vshard/router/init.lua
>> index 7e765fa..df5b343 100644
>> --- a/vshard/router/init.lua
>> +++ b/vshard/router/init.lua
>> @@ -127,10 +127,23 @@ local function discovery_f(module_version)
>> +            -- Renew replicasets object in case of reconfigure
>> +            -- and reload events.
>
> 5. You do not renew here anything.
>
>> +            if M.replicasets ~= old_replicasets then
>> +                break
>> +            end
I have rewritten the comment. The replicasets variable captured by the
for loop should be updated by calling `break` and exiting the for loop.

  reply	other threads:[~2018-06-25 12:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 12:47 [tarantool-patches] [PATCH 0/2][vshard] preserve route map AKhatskevich
2018-06-15 12:47 ` [tarantool-patches] [PATCH 1/2] Preserve route_map on router.cfg AKhatskevich
2018-06-21 12:54   ` [tarantool-patches] " Vladislav Shpilevoy
2018-06-25 12:48     ` Alex Khatskevich
2018-06-15 12:47 ` [tarantool-patches] [PATCH 2/2] Fix discovery/reconfigure race AKhatskevich
2018-06-21 12:54   ` [tarantool-patches] " Vladislav Shpilevoy
2018-06-25 12:48     ` Alex Khatskevich [this message]
2018-06-26 11:11       ` Vladislav Shpilevoy
2018-06-26 14:03         ` Alex Khatskevich
2018-06-27 11:45           ` Vladislav Shpilevoy
2018-06-27 19:50             ` Alex Khatskevich
2018-06-28 19:41               ` Vladislav Shpilevoy
2018-06-21 12:54 ` [tarantool-patches] Re: [PATCH 0/2][vshard] preserve route map Vladislav Shpilevoy
2018-06-25 11:52   ` Alex Khatskevich

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=f6e438ae-64af-7cb5-bf99-938e821f21c8@tarantool.org \
    --to=avkhatskevich@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH 2/2] Fix discovery/reconfigure race' \
    /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