Yann Hamon

We had the same issue a few weeks ago - it turned out to be an issue with newer, Nitro instances (c5, t3, ...) - AWS investigated and claims to...

Hi @zekker6 , thanks a lot! I like the idea, I need to think about it a little bit - wondering if this makes sense when dumping all databases for...

Hi @kurtmc , thanks for the report! It looks like this is not supported yet. What would be the expected behaviour - that the Stream is recreated on the target...

Hi @linydquantil , I m assuming 1.resp is db1 and 2.resp is db2?

Could you actually give a shot at reporting against redis-cli? It looks like it might have its own timeouts... a file with garbage content that would allow to reproduce this...

One simpler thing we could try is set the Zset in multiple small commands rather than a single large one. Still this is unusual :(

I will consider writing an improvement to import large zsets/maps in multiple commands :bow:

Alright I'm able to reproduce https://github.com/yannh/redis-dump-go/compare/integration-tests?expand=1 Using my mock zset I m starting to see issues once the zset has around 1M entries. ```-> Waiting for Redis to start... ->...

Released v0.5.0 - long commands are now broken down into batches to avoid errors during imports. Also: there is an acceptance tests that generates, imports, dumps a ZSET with 1M...

Yes, that would be nice, thanks for the suggestion :) Might work on this at some point, would also accept a patch!