gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Tracking: fix behavior when switchinig from normal to BCAST.

Browse Source
This commit is contained in:
antirez 2020-02-14 14:17:10 +01:00
parent 6922ccc0b9
commit f6e32a832f
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/tracking.c
View File

@ -269,7 +269,17 @@ void trackingInvalidateKey(robj *keyobj) {
uint64_t id; uint64_t id;
memcpy(&id,ri.key,sizeof(id)); memcpy(&id,ri.key,sizeof(id));
client *c = lookupClientByID(id); client *c = lookupClientByID(id);
if (c == NULL || !(c->flags & CLIENT_TRACKING)) continue; /* Note that if the client is in BCAST mode, we don't want to
* send invalidation messages that were pending in the case
* previously the client was not in BCAST mode. This can happen if
* TRACKING is enabled normally, and then the client switches to
* BCAST mode. */
if (c == NULL ||
!(c->flags & CLIENT_TRACKING)||
c->flags & CLIENT_TRACKING_BCAST)
{
continue;
}
sendTrackingMessage(c,sdskey,sdslen(sdskey),0); sendTrackingMessage(c,sdskey,sdslen(sdskey),0);
} }
raxStop(&ri); raxStop(&ri);