BUG/MINOR: peers: always update the stksess shard number on incoming updates

If shards are in use, we must fill the shard number on incoming updates,
otherwise some entries are assigned shard number zero, and may be broadcast
everywhere once updated, instead of being sent only to the peers having the
same shard number.

This fixes commit 36d156564 ("MINOR: peers: Support for peer shards"). No
backport is needed.

diff --git a/src/peers.c b/src/peers.c
index 5245bb71558e131af7639c9a8f2d5073e5ab85af..aa0ab9734e9314838da7def7315305ea0e5b9ad3 100644 (file)
--- a/src/peers.c
+++ b/src/peers.c
@@ -1808,6 +1808,8 @@ static int peer_treat_updatemsg(struct appctx *appctx, struct peer *p, int updt,
                *msg_cur += keylen;
        }
 
+       newts->shard = stktable_get_key_shard(st->table, newts->key.key, keylen);
+
        /* lookup for existing entry */
        ts = stktable_set_entry(st->table, newts);
        if (ts != newts) {