From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Alex Khatskevich <avkhatskevich@tarantool.org>, tarantool-patches@freelists.org Subject: [tarantool-patches] Re: [PATCH 2/2] Fix discovery/reconfigure race Date: Wed, 27 Jun 2018 14:45:27 +0300 [thread overview] Message-ID: <cfaa91ab-1a30-ee1c-55d4-e702d7ef0f0a@tarantool.org> (raw) In-Reply-To: <7790cb4a-ff5e-99bf-03bc-996fea379185@tarantool.org> Thanks for the fixes! See 2 comments below. > commit bc90c3db5f5b1b663c747b8c2829fc8528af70cf > Author: AKhatskevich <avkhatskevich@tarantool.org> > Date: Thu Jun 14 16:03:09 2018 +0300 > > Fix discovery/reconfigure race > > This commit prevents discovery fiber from discovering old replicasets > and spoiling `route_map`. > > diff --git a/test/router/router.result b/test/router/router.result > index 5643f3e..36d54bf 100644 > --- a/test/router/router.result > +++ b/test/router/router.result > @@ -1095,6 +1095,55 @@ for bucket, old_rs in pairs(bucket_to_old_rs) do > end; > --- > ... > +-- > +-- Check route_map is not filled with old replica objects after > +-- reconfigure. > +-- > +-- Simulate long `callro`. > +vshard.router.internal.errinj.ERRINJ_LONG_DISCOVERY = true; > +--- > +... > +while not vshard.router.internal.errinj.ERRINJ_LONG_DISCOVERY == 'waiting' do 1. Why 'not value == needed_value'? Why not 'value ~= needed_value'? And how does it work? I checked this thing in Lua and got these results: -- Before cycle tarantool> not true == 'waiting' --- - false ... -- After 'waiting' is set tarantool> not 'waiting' == 'waiting' --- - false ... So this cycle is never run. And I proved it with putting assert(false) into the first line - the test passed as well: [001] +++ router/router.reject Wed Jun 27 14:39:30 2018 [001] @@ -1104,6 +1104,7 @@ [001] --- [001] ... [001] while not vshard.router.internal.errinj.ERRINJ_LONG_DISCOVERY == 'waiting' do [001] + assert(false) [001] vshard.router.discovery_wakeup() [001] fiber.sleep(0.02) [001] end; [001] Please, investigate why your test passes even without this cycle again. > + vshard.router.discovery_wakeup() > + fiber.sleep(0.02) > +end; > +--- > +... > +vshard.router.cfg(cfg); > +--- > +... > +route_map = vshard.router.internal.route_map > +for bucket_id, _ in pairs(route_map) do > + route_map[bucket_id] = nil > +end; 2. Why not just 'vshard.router.internal.route_map = {}' ?
next prev parent reply other threads:[~2018-06-27 11:45 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 2018-06-26 11:11 ` Vladislav Shpilevoy 2018-06-26 14:03 ` Alex Khatskevich 2018-06-27 11:45 ` Vladislav Shpilevoy [this message] 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=cfaa91ab-1a30-ee1c-55d4-e702d7ef0f0a@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=avkhatskevich@tarantool.org \ --cc=tarantool-patches@freelists.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