00:02:44 GMT <znn> has anyone seen this error before? https://gist.github.com/uunsamp/6d6720e2be84766e756d6fb59f00caaf
01:32:32 GMT <znn> i keep running docker rm $(docker ps -a -q) and docker rmi $(docker images -q)
01:32:38 GMT <znn> and then rebuilding with docker-compose up
01:32:42 GMT <znn> this is taking a really long time
01:32:51 GMT <znn> wrong chan
06:11:15 GMT <webchat-1969> well...another day, another try
06:11:20 GMT <webchat-1969> anyone that could help me understand a few things about redis clusters?
09:34:58 GMT <Numline1> webchat-1969 I think it would be best if you asked the question directly
09:35:11 GMT <Numline1> don't expect people to say "yes" without asking the question first :]
09:37:08 GMT <webchat-1969> Numline1: not many people show his head around here...
09:37:23 GMT <Numline1> webchat-1969 more reason to ask first :]
09:38:14 GMT <webchat-1969> AFAIK, a cluster split slots between masters, who could replicate to their replicas
09:38:53 GMT <webchat-1969> is there any way to "automatically" reallocate slots without using redis-trib? (self-mantained cluster)
09:39:33 GMT <webchat-1969> is there a way to prevent any replica becoming a master? (but wait until master come back)
09:40:23 GMT <webchat-1969> if each node has their own config/data files, and one master goes down...another instance with the same files configured will it "became" the old one?
09:59:12 GMT <webchat-1969> Numline1: see? same result, much more typing :P
10:35:03 GMT <labsy> hi all
10:35:24 GMT <labsy> is it a normal behavour for a slave to have its master_link_status: down when master is doing wait_bgsave?
11:15:04 GMT <labsy> anyone?
11:15:07 GMT <labsy> is it a normal behavour for a slave to have its master_link_status: down when master is doing wait_bgsave?
12:50:29 GMT <labsy> this chan sucks
13:11:51 GMT <armin> ohai!
14:42:15 GMT <minus> sup
18:26:22 GMT <DallOner> Hello everyone