You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NRedisStack Version:
v0.8.0, also tried upgrading to v0.11.0
Redis Stack Version:
Not using a Redis Stack image. We've buiilt our own image for cluster, using only the modules we need.
Redis cluster v7.2.1 with RediSearch v2.8.6 and RedisJSON v2.6.6
Description:
Aggregate cursor read fails, saying "cursor not found"
Rarely, it will work and return the next set of results, only to fail on the next iteration.
From the cli, I can use aggregate and cursor read to successfully iterate over all the results.
I have tried some tests where I will run the aggregate from NRedisStack and cursor read from cli, and vice-versa. It usually fails with "cursor not found". In the case where the cli cursor read works with NRedisStack's aggregate, I am able to keep using the cursor and iterate over all the results.
From these details, it appears that NRedisStack's aggregate and cursor commands are served by random nodes in the cluster, but only the node that did the aggregate command can do the subsequent cursor commands.
The text was updated successfully, but these errors were encountered:
NRedisStack Version:
v0.8.0, also tried upgrading to v0.11.0
Redis Stack Version:
Not using a Redis Stack image. We've buiilt our own image for cluster, using only the modules we need.
Redis cluster v7.2.1 with RediSearch v2.8.6 and RedisJSON v2.6.6
Description:
Aggregate cursor read fails, saying "cursor not found"
Rarely, it will work and return the next set of results, only to fail on the next iteration.
From the cli, I can use aggregate and cursor read to successfully iterate over all the results.
I have tried some tests where I will run the aggregate from NRedisStack and cursor read from cli, and vice-versa. It usually fails with "cursor not found". In the case where the cli cursor read works with NRedisStack's aggregate, I am able to keep using the cursor and iterate over all the results.
From these details, it appears that NRedisStack's aggregate and cursor commands are served by random nodes in the cluster, but only the node that did the aggregate command can do the subsequent cursor commands.
The text was updated successfully, but these errors were encountered: