04:10:22 GMT <sembiance> wow
04:10:33 GMT <sembiance> nobody said a single thing in here yesterday.
04:10:40 GMT <sembiance> all day went by, not a single word.
04:10:53 GMT <sembiance> looks like I'm the first to spead today heh
04:11:09 GMT <sembiance> guess that's what happens on an IRC channel about a product that is rock solid and awesome. no need to go get help heh
11:56:34 GMT <jacobog> Hello, I'm working on automating the creation of redis installs (primary, slave, sentinel) with ansible. I am aware of the issues derived from mantaining the state of the installs in the configuration files (sentinel.conf, redis.conf). I'm also aware of this post: http://antirez.com/news/54 I am looking any tips on how to solve this issues. Which strategies have used other administrators? Thanks.
14:35:55 GMT <junsionzhang> hello
14:36:11 GMT <junsionzhang> is any body there ?
14:53:23 GMT <junsionzhang> @all
14:53:54 GMT <junsionzhang> @junsionzhang
14:59:13 GMT <zpojqwfejwfhiunz> hi, on IRC we don't preface nicks with '@'
14:59:43 GMT <zpojqwfejwfhiunz> oh, he left already
16:39:01 GMT <andrewrk> I'm trying to run redis-trib.rb reshard and getting: [WARNING] Node 127.0.0.1:7001 has slots in migrating state (5471).
16:39:15 GMT <andrewrk> but it doesn't seem to be resolving itself
16:39:39 GMT <andrewrk> redis-trib.rb fix says [ERR] Sorry, Redis-trib can't fix this slot yet (work in progress).
21:13:07 GMT <jj995> `docker pull redis` results in error `no matching manifest for linux/amd64 in the manifest list entries`
21:13:21 GMT <jj995> `docker pull redis:4.0.2` works
21:14:01 GMT <jj995> is docker redis latest broken a known issue?  I know I shouldn't be using latest in production, but this is currently breaking a lot of production
21:15:32 GMT <jj995> can someone in this chat please confirm `docker pull redis` doesn't work?
21:31:43 GMT <jj995> Am I off topic by discussing the latest official redis docker being broken?  I'm confused why nobody has responded
21:33:52 GMT <zpojqwfejwfhiunz> please try a docker support channel
21:52:01 GMT <andrewrk> [ERR] Calling MIGRATE: ERR Syntax error, try CLIENT (LIST | KILL | GETNAME | SETNAME | PAUSE | REPLY)
21:52:06 GMT <andrewrk> when I use redis-trib.rb
21:52:19 GMT <andrewrk> on 4.0.4. is this a known bug?
23:00:23 GMT <zpojqwfejwfhiunz> andrewrk:
23:00:27 GMT <zpojqwfejwfhiunz> https://github.com/antirez/redis/issues/4272
23:02:16 GMT <andrewrk> zpojqwfejwfhiunz, I ended up finding that issue, and resolved the issue. Thanks.
23:02:43 GMT <andrewrk> if redis is going to ship with ruby code it should lock the dependency versions
23:05:04 GMT <minus> whatever the reason is that redis-trib is written in ruby in the first place
23:08:38 GMT <zpojqwfejwfhiunz> I agree
23:09:00 GMT <zpojqwfejwfhiunz> there's a bunch of TCL too in the tests with Ruby slowly creeping in as well
23:09:58 GMT <minus> quickly glancing over the script it looks like it could've been C too
23:12:11 GMT <zpojqwfejwfhiunz> the problem it solves is not hard, and it does not solve the problem well
23:12:31 GMT <zpojqwfejwfhiunz> to reframe Phil Wadler's famous quote
23:12:33 GMT <andrewrk> the official docs encourage users to use it
23:13:34 GMT <zpojqwfejwfhiunz> https://github.com/antirez/redis/issues/3199#issuecomment-328110604
23:13:48 GMT <zpojqwfejwfhiunz> looks like it's being deprecated
23:14:26 GMT <andrewrk> that comment doesn't seem to understand how version locking works
23:14:46 GMT <andrewrk> I mean it will probably be more well maintained in the upcoming C version
23:15:00 GMT <zpojqwfejwfhiunz> here's the 4.2 roadmap BTW https://gist.github.com/antirez/a3787d538eec3db381a41654e214b31d