From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, Alex Khatskevich <avkhatskevich@tarantool.org> Subject: [tarantool-patches] Re: [PATCH 1/4] Fix races related to object outdating Date: Wed, 1 Aug 2018 15:36:34 +0300 [thread overview] Message-ID: <39dccfbe-8d6a-ffe7-b841-efa0c5352697@tarantool.org> (raw) In-Reply-To: <1eeb6917-0153-919d-de56-c21052ea42f9@tarantool.org> Hi! Thanks for the patch! See 2 comments below. > diff --git a/vshard/router/init.lua b/vshard/router/init.lua > index 142ddb6..1a0ed2f 100644 > --- a/vshard/router/init.lua > +++ b/vshard/router/init.lua > @@ -88,15 +94,18 @@ local function bucket_discovery(bucket_id) > log.verbose("Discovering bucket %d", bucket_id) > local last_err = nil > local unreachable_uuid = nil > - for uuid, replicaset in pairs(M.replicasets) do > - local _, err = > - replicaset:callrw('vshard.storage.bucket_stat', {bucket_id}) > - if err == nil then > - bucket_set(bucket_id, replicaset) > - return replicaset > - elseif err.code ~= lerror.code.WRONG_BUCKET then > - last_err = err > - unreachable_uuid = uuid > + for uuid, _ in pairs(M.replicasets) do > + -- Handle reload/reconfigure. > + replicaset = M.replicasets[uuid] 1. Please, explain, how is it possible, that before this line M.replicasets[uuid] can become nil. You iterate here over M.replicasets and on the previous line in '_' you have stored replicaset. How can here 'replicaset' differ from '_'? It has nothing in common with 'reload/reconfigure' case since you always iterate over M.replicasets - the most actual list of replicasets. Maybe you thought that pairs() stores its first argument into a temporary variable but looks like it is not. I checked it with a simple test: a = {} a.objs = {1, 2, 3, 4, 5} for k, v in pairs(a.objs) do print(a.objs[k]) if k == 2 then a.objs = {6, 7, 8, 9, 10} end end Output: 1 2 8 9 10 --- ... > + if replicaset then > + local _, err = > + replicaset:callrw('vshard.storage.bucket_stat', {bucket_id}) > + if err == nil then > + return bucket_set(bucket_id, replicaset.uuid) > + elseif err.code ~= lerror.code.WRONG_BUCKET then > + last_err = err > + unreachable_uuid = uuid > + end > end > end > local err = nil > @@ -513,27 +522,28 @@ local function router_cfg(cfg) > end > box.cfg(box_cfg) > log.info("Box has been configured") > - M.connection_outdate_delay = cfg.connection_outdate_delay > - M.total_bucket_count = total_bucket_count > - M.collect_lua_garbage = collect_lua_garbage > - M.current_cfg = new_cfg > -- Move connections from an old configuration to a new one. > -- It must be done with no yields to prevent usage both of not > -- fully moved old replicasets, and not fully built new ones. > - lreplicaset.rebind_replicasets(new_replicasets, M.replicasets, > - M.connection_outdate_delay) > - M.replicasets = new_replicasets > + lreplicaset.rebind_replicasets(new_replicasets, M.replicasets) > -- Now the new replicasets are fully built. Can establish > -- connections and yield. > for _, replicaset in pairs(new_replicasets) do > replicaset:connect_all() > end > + lreplicaset.wait_masters_connect(new_replicasets) > + lreplicaset.outdate_replicasets(M.replicasets, cfg.connection_outdate_delay) > + M.connection_outdate_delay = cfg.connection_outdate_delay > + M.total_bucket_count = total_bucket_count > + M.collect_lua_garbage = collect_lua_garbage > + M.current_cfg = cfg > + M.replicasets = new_replicasets > -- Update existing route map in-place. > - for bucket, rs in pairs(M.route_map) do > + local old_route_map = M.route_map > + M.route_map = {} > + for bucket, rs in pairs(old_route_map) do > M.route_map[bucket] = M.replicasets[rs.uuid] 2. Why do you need to save old_route_map into a separate variable? You can update M.route_map in place like it was done before. It is not? You fill the new route_map with exactly the same keys (maybe with different values, but it does not affect 'for' iteration). Moreover, when you create a new route_map instead of resetting the old, you double the memory. For huge bucket count it can be noticeable. > end > - > - lreplicaset.wait_masters_connect(new_replicasets) > if M.failover_fiber == nil then > lfiber.create(util.reloadable_fiber_f, M, 'failover_f', 'Failover') > end
next prev parent reply other threads:[~2018-08-01 12:36 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-30 8:56 [tarantool-patches] [PATCH v4] vshard module reload AKhatskevich 2018-07-30 8:56 ` [tarantool-patches] [PATCH 1/4] Fix races related to object outdating AKhatskevich 2018-07-30 11:55 ` [tarantool-patches] " Vladislav Shpilevoy 2018-07-30 16:46 ` Alex Khatskevich 2018-07-30 17:50 ` Vladislav Shpilevoy 2018-07-31 11:05 ` Alex Khatskevich 2018-08-01 12:36 ` Vladislav Shpilevoy [this message] 2018-08-01 17:44 ` Alex Khatskevich 2018-08-02 11:51 ` Vladislav Shpilevoy 2018-07-30 8:56 ` [tarantool-patches] [PATCH 2/4] Refactor reloadable fiber AKhatskevich 2018-07-30 11:55 ` [tarantool-patches] " Vladislav Shpilevoy 2018-07-31 11:24 ` Alex Khatskevich 2018-07-31 11:30 ` Alex Khatskevich 2018-08-01 11:54 ` Vladislav Shpilevoy 2018-07-30 8:56 ` [tarantool-patches] [PATCH 3/4] tests: separate bootstrap routine to a lua_libs AKhatskevich 2018-08-01 12:03 ` [tarantool-patches] " Vladislav Shpilevoy 2018-07-30 8:56 ` [tarantool-patches] [PATCH 4/4] Introduce storage reload evolution AKhatskevich 2018-07-30 11:55 ` [tarantool-patches] " Vladislav Shpilevoy 2018-07-31 11:29 ` Alex Khatskevich 2018-07-31 11:33 ` Alex Khatskevich 2018-08-01 12:36 ` Vladislav Shpilevoy 2018-08-01 18:09 ` Alex Khatskevich 2018-08-02 11:40 ` Vladislav Shpilevoy 2018-08-02 11:46 ` Vladislav Shpilevoy 2018-08-06 10:59 ` Alex Khatskevich 2018-08-06 15:36 ` Vladislav Shpilevoy 2018-08-06 16:08 ` Alex Khatskevich 2018-08-06 17:18 ` Vladislav Shpilevoy 2018-08-07 9:14 ` Alex Khatskevich 2018-08-08 10:35 ` Vladislav Shpilevoy 2018-08-01 14:07 ` [tarantool-patches] [PATCH] Check self arg passed for router objects AKhatskevich
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=39dccfbe-8d6a-ffe7-b841-efa0c5352697@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=avkhatskevich@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH 1/4] Fix races related to object outdating' \ /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