[10:43:44] <anomie> legoktm: I'm seeing "read error on connection" coming back from redis.
[10:44:03] <anomie> in response to the call to $conn->multi().
[10:44:06] <legoktm> nutcracker issue then?
[10:44:35] <legoktm> is it a specific backend?
[10:45:25] <anomie> Some commands work fine, e.g. ping(). Others do this. Do we have some sort of command whitelist set up in our redis?
[10:50:52] <AaronSchulz> no whitelist afaik
[10:54:04] <anomie> ->ping() works, ->time() doesn't, ->info() doesn't, ->echo() doesn't. And, critically, ->multi() doesn't.
[10:56:17] <AaronSchulz> multi() may be a temproxy bug
[10:56:47] <AaronSchulz> for info() it at least makes sense that it doesn't work due to the proxying/hashing
[10:57:20] -*- AaronSchulz noticed that before
[10:57:59] <AaronSchulz> https://github.com/twitter/twemproxy/blob/master/notes/redis.md
[10:59:12] <Reedy> Almost sounds like we need an extra MW class a wrapper
[10:59:55] <AaronSchulz> multi() is not supported there, so that explains
[11:00:03] <AaronSchulz> CA can clearly just use set() for the tokens for now
[11:00:36] <AaronSchulz> I'll make a patch for that, maybe core, and poke at cas() later
[11:01:06] <anomie> Well, there we go then. RedisBagOStuff doesn't fully work with twemproxy because it doesn't support multi/exec, watch/unwatch, or info.
[11:01:32] <hoo> AaronSchulz: Thanks