03:10:01 GMT <xep> what a day... upgraded a Redis tier at work that was still using 2.8.13 to 3.0.7
03:10:21 GMT <xep> I'd been working up to it for a while because I wanted the smoothest possible transition without shutting down services that relied on it
03:10:55 GMT <xep> the twemproxy fork with andyqzb's Redis Sentinel patch was instrumental in making this a success for the case of clients not aware of Sentinel
03:11:18 GMT <xep> nice performance improvements, upper bound on latency saw a nice drop.
03:12:27 GMT <xep> next need to more or less repeat the same thing but swap the drives out for SSDs. a bit over 60GB of data between 20 shards, took a while to do a shutdown on all the slaves and to start them back up again
03:13:49 GMT <xep> at some point with all the syncs happening I hit about 70k packets / second on one of the machines. apparently ops has put much nicer network hardware in these days.
07:22:47 GMT <Lokesh> Hi...Can I ask queries to scale redis
07:36:21 GMT <Lokesh> Can I have a voice call..pls share no
11:45:19 GMT <Inge-> xep: cool
13:35:19 GMT <Brijesh1> Is it possible to make non persistence redis with master-slave
13:35:45 GMT <antirez_> itamarhaber: maybe you understand this issue better than me? I saw your +1 on it -> https://github.com/antirez/redis/pull/3235
13:38:31 GMT <Brijesh1> antirez i have created the master and slave on the same machine but want by redis to non persistence
13:40:01 GMT <*> antirez_  can't help right now, sorry
13:42:12 GMT <Brijesh1> thanks ..np
13:50:02 GMT <Brijesh1> redis is single threaded . so if i have a 4 core cpu , it will only use only single core for processing or will it fork it that single core is 100% utilized
13:50:48 GMT <Brijesh1> if that single core is 100% utilized
14:01:42 GMT <colo-work> redis is a single process (exception: forking a child for background-saving the database(s))
14:03:13 GMT <Brijesh1> it will fork only if we are using redis as persistence
17:06:04 GMT <antirez_> progresses regarding the Sentinel bug introduced with 3.2 -> https://github.com/antirez/redis/issues/3285
18:48:08 GMT <madsage> redis 3.2 cluster support requirepass?
18:48:57 GMT <madsage> i am reading from redis google groups. i wanted to use redis-trib.rb but there is no option for requirepass auth
18:49:36 GMT <madsage> now i'm seeing chatter about dont use requirepass in cluster, its insecure anyways?
18:49:54 GMT <madsage> i get it. its plaintext
18:51:07 GMT <madsage> my redis is on private network anyways. guess i'm still curious if requirepass is not supported by redis clustering
18:53:15 GMT <madsage> Long story short, for now we'll leave things as they are, that is, you  can't enable authentication in a cluster if you want to talk to the  cluster with redis-trib. Later there will be time to understand what  to do, if to improve the authentication system, or to remove it from  Cluster at all.   Salvatore
18:55:39 GMT <madsage> grrrr. i joust brought up 9 nodes with requirepass
18:55:55 GMT <madsage> s/joust/just
21:54:47 GMT <rakm> is there a way to check what conf file is being used from inside redis-cli?