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

Add more info in the unblockClientFromModule() function.

Browse Source
This commit is contained in:
antirez 2020-01-29 12:47:50 +01:00
parent bf53f9280a
commit 17ff3173d6
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/module.c
View File

@ -4282,7 +4282,13 @@ void unblockClientFromModule(client *c) {
* not implemented (or it was, but RM_UnblockClient was not called from * not implemented (or it was, but RM_UnblockClient was not called from
* within it, as it should). * within it, as it should).
* We must call moduleUnblockClient in order to free privdata and * We must call moduleUnblockClient in order to free privdata and
* RedisModuleBlockedClient */ * RedisModuleBlockedClient.
*
* Note that clients implementing threads and working with private data,
* should make sure to stop the threads or protect the private data
* in some other way in the disconnection and timeout callback, because
* here we are going to free the private data associated with the
* blocked client. */
if (!bc->unblocked) if (!bc->unblocked)
moduleUnblockClient(c); moduleUnblockClient(c);