Multi-exec issue on result
See original GitHub issuemost of the times during the start of my node instance, I get this
[ [ null, 'OK' ], [ null, '{"base":[{"base_id":1}]}' ] ]
for this command
redisClient.multi().select(5).get(key).exec()
but for some, I get this
[ [ null, 'O' ], [ null, 'K' ] ]
looks like the result of select is being broken into 2. any ideas where this problem might be?
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
How to get the result of executing curl_multi_exec?
Problem set recommendations for a student who has taken classes through Calc III, but has very weak fundamentals.
Read more >Redshift - Multi Execute - Spaces - Confluence
This Snap is used to execute multiple Redshift SQL statements sequentially inside of a single BEGIN and END transaction for each input document....
Read more >Purpose of transactions (watch/multi/exec) for RedisGraph ...
I've got a question about concurrent graph modifications with ... offers the ability to receive back individual query results / responses.
Read more >aioredis 1.3.0 documentation - Read the Docs
Issue Tracker: https://github.com/aio-libs/aioredis/issues ... Result messages decoding · Multi/Exec transactions · Pub/Sub mode · Sentinel client.
Read more >Re: Redis pipeline vs multi/exec - Google Groups
question basically), the block of commands is executed in isolation as ... client will just "a" as a result of the command, but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
i am trying to isolate code since project is quite big.
if i isolate, the problem does not exist. but if i run it together with everything else, problem shows up 100% I am inclined to think that there might be other stuff causing this but it is difficult to trace. it only shows up during startup, where the server tries to do lot of initialization like fetching a bunch of wsdl for a SOAP feature.
strange enough, when i put a 2seconds timeout before fetching from redis, it works. this is not ideal as i need the cache as early as possible during startup. any clue on how to dig deeper?
Kelvin Chua
On Tue, Nov 1, 2016 at 7:40 PM, Zihua 子骅 notifications@github.com wrote:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 7 days if no further activity occurs, but feel free to re-open a closed issue if needed.