11:44:27 GMT <adac> Do you think that can work badboy_ ? https://github.com/ahfeel/rancher-redis-cluster
11:44:55 GMT <adac> i was just remembering that you said some time ago redis i not really good with working with docker yet
11:45:23 GMT <badboy_> no idea
11:45:26 GMT <badboy_> I don't use Docker
11:46:08 GMT <badboy_> from the readme it seems that is not "Redis Cluster"
11:47:08 GMT <badboy_> it is just master+slave + sentinel
12:06:41 GMT <adac> badboy_, Ok I see yes. thanks for your opinion!
12:17:24 GMT <adac> badboy_, Is there actually some effort being done already to make redis cluster also compatible with docker?
12:17:50 GMT <badboy_> no
12:18:06 GMT <badboy_> well, it is docker-compatible if you use --net=host :P
12:18:14 GMT <adac> hehe
12:18:24 GMT <minus> tl;dr use --net=host if your application in docker supports it
12:19:08 GMT <adac> need to have a look at this see if it can work with rancher by enabling --net=host
12:59:23 GMT <*> [gnubie]  waves
13:03:23 GMT <*> [gnubie]  waves
13:03:50 GMT <[gnubie]> please bear with me as i am new to redis. may i know if redis v4.0.1 backward compatible to redis v3.x?
13:04:22 GMT <badboy_> yes
13:05:34 GMT <[gnubie]> badboy_: thank you. i am trying to use redis as a broker before logstash. basically, journalbeat will use redis v4.0.1 as its output.
15:42:44 GMT <seion> is it possible to sort a set like this... I have a set which contains a bunch of strings joined together with :   so  somerandomstring:anotherrandomstring:COUNTINT
15:42:50 GMT <seion> I would like to sort by countint
15:51:50 GMT <minus> Maybe with a sorted set an lexical stuff, or with a lua script
15:52:15 GMT <minus> Not sure if either are a good idea
15:53:38 GMT <seion> here is an example member "dbb19a51f1cc327c400e9e8c1cb34003f0d2bd5bacf2c0cc4801c33d85:4150afd418c6383ba55c12dc0b2c53f859d50081bd1a5ffeb28719d7de:13716"
15:53:54 GMT <seion> I want to sort on that last number
15:56:59 GMT <minus> Redis itself can't really do that
15:57:19 GMT <seion> :/ oh well I guess ill pull it into the code and sort it
15:58:36 GMT <ahfeel_> seion: and can't you store it with the int first ?
15:58:58 GMT <seion> I would, but this is an already implemented application I am pulling data from
18:18:45 GMT <MacWinner> is there any performance benefit of using different dataabases within a redis instance?  or is it purely an organizational thing?
18:38:03 GMT <treehug88> I think I recall reading that the numbered database thing was something the author regretted adding, which is why they don't get names and why there has been talk of deprecating them: https://groups.google.com/forum/#!topic/redis-db/vS5wX8X4Cjg/discussion
18:38:05 GMT <treehug88> "I understand how this can be useful, but unfortunately I consider
18:38:05 GMT <treehug88> Redis multiple database errors my worst decision in Redis design at
18:38:05 GMT <treehug88> all... without any kind of real gain, it makes the internals a lot
18:38:05 GMT <treehug88> more complex."
18:38:21 GMT <treehug88> (sorry for the paste) that's to you MacWinner
18:38:56 GMT <MacWinner> treehug88, thanks!
18:39:27 GMT <treehug88> yeah and I realize I didn't technically answer your question
18:39:59 GMT <MacWinner> i've been seeing some stuff on stackovervlow that the extra db's dont really have a good reason for existing
18:41:33 GMT <treehug88> you're welcome
20:49:54 GMT <RaySl> was looking at my redis stats and saw `instantaneous_ops_per_sec: 210699` which seems insanely high... amI reading this value right?
20:51:55 GMT <minus> 210966 commands per second