I have an issue while trying to interact with Redis in those conditions:
1) Redis instance with Redisearch module,
2) Create node-redis client before Redis module fork is ongoing,
3) Redis module fork is on-going
The behaviour that I get is that "send_command" stays idle until the fork stops.
When the fork ends I get this error:
debug mode (node-redis) ->
Redis connection is gone from end event
client err ->
AbortError: Redis connection lost and command aborted. It might have been processed.
After I get this error the commands from the same client (without creating a new client) come back to works fine.
A bit delayed, I know, but would you mind uploading a code snippet for me to have a look at?
Currently thinking of writing a test for the bug, then working based off that.
Issue
Hi everyone,
I have an issue while trying to interact with Redis in those conditions: 1) Redis instance with Redisearch module, 2) Create node-redis client before Redis module fork is ongoing, 3) Redis module fork is on-going
The behaviour that I get is that "send_command" stays idle until the fork stops. When the fork ends I get this error: debug mode (node-redis) ->
Redis connection is gone from end event
client err ->AbortError: Redis connection lost and command aborted. It might have been processed.
After I get this error the commands from the same client (without creating a new client) come back to works fine.
On every fork, I got the same behaviour.
Environment
v14.15.1
6.0.4
1.6.15
3.2
Server 128GB RAM, 8 Core, Debian