Does Jedis support to using pipeline to access Redis cluster?

[cwh...@gmail.com]

I did not find any test cases about it, and also find that JedisCluster class does not support #pipelined method from the source code of Jedis2.5.2.

[임정택]

Yes, currently JedisCluster doesn't support pipeline.
We yet don't have plan to implement it, so your contribution is very appreciated!

Thanks.

Jungtaek Lim(HeartSaVioR)

[임정택]

Btw, JedisCluster should take care of MOVED / CROSSSLOT, so pipeline behavior would not same to normal Jedis.

It makes us hard to implement it.

2014년 8월 8일 금요일 오후 11시 36분 27초 UTC+9, 임정택 님의 말:

[Jonathan Leibiusky]

Mmm... yeah. Thinking about it seems like the implementation would be extremely complex and the behavior somehow weird.

We should check if there are libraries that are dealing with this already. Maybe redis-rb or the python library? I don't really know which libraries have already cluster support.

--
You received this message because you are subscribed to the Google Groups "Jedis" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jedis_redis...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark V]

Maybe a solution to only support when all Pipeline commands go to same node would be OK. (  when all pipeline command have same consistant hashing {} key) 

Dne petek, 08. avgust 2014 17:27:42 UTC+2 je oseba Jonathan L. napisala:

[Daniel Guo]

Could we first calculate the slots that each key belongs to using CRC16, and then pipeline the keys in the same slot?

[임정택]

Maybe no, let's say you're sending 10 commands to Redis with Pipelining, moving slot may intrude into your sequential commands.

Then first N commands run fine, but second 10 - N commands throws MOVED, which we cannot handle easily.

2015년 3월 29일 일요일 오후 2시 58분 29초 UTC+9, Daniel Guo 님의 말: