Unhandled promise rejection triggered in DoublyLinkedList after executeTask()

[udnes99]

Description

We just detected an unhandled promise rejection that was triggered while issuing a command or a .execute() using a pool instance. Due to limited stack trace, I am not sure if it was a dedicated client obtained by .execute() or just a client retrieved for the execution of a single command. I am not that familiar with the internals of the Redis SDK, but I am guessing some kind of race condition within the library related to the acquisition and release of client instances for tasks, or some bug in the linked list.

Node.js Version

22.18.0

Redis Server Version

7.4.0

Node Redis Version

5.8.0

Platform

Linux

Logs

TypeError: Cannot set properties of undefined (setting 'next')
  File "/app/node_modules/.pnpm/@redis+client@5.8.0/node_modules/@redis/client/dist/lib/client/linked-list.js", line 76, col 32, in DoublyLinkedList.remove
    node.previous.next = node.next;
  File "/app/node_modules/.pnpm/@redis+client@5.8.0/node_modules/@redis/client/dist/lib/client/pool.js", line 262, col 28, in #returnClient
    this.#clientsInUse.remove(node);
  File "/app/node_modules/.pnpm/@redis+client@5.8.0/node_modules/@redis/client/dist/lib/client/pool.js", line 248, col 50
    .finally(() => this.#returnClient(node));
  File "<anonymous>"

[nkaradzhov]

Hi @udnes99, thanks for raising this issue. I can easily patch the current TypeError that you are experiencing, but i have the suspicion that there is another problem that is hiding here. And that problem is gonna be hard to find tbh. If you are able to narrow it down somehow on your side, that would be great.

[udnes99]

Hi @udnes99, thanks for raising this issue. I can easily patch the current TypeError that you are experiencing, but i have the suspicion that there is another problem that is hiding here. And that problem is gonna be hard to find tbh. If you are able to narrow it down somehow on your side, that would be great.

I understand! Like I said, I am not that familiar with the internals of this library. I am not sure what the conditions are for triggering it; it seems sporadic on our side. I suspect there is some sort of race condition. I can try to look through the code, though.