03:40:35 GMT <cornfeedhobo> are different databases handled in different threads?
08:43:10 GMT <minus> cornfeedhobo: no
18:29:10 GMT <spinnix> I can't bind ReJSON as module with my config at Redis 3.2.1. Config line: loadmodule /var/redis/rejson.so ERR: Bad directive or wrong number of arguments
18:50:32 GMT <alexasdasdasd> hey guys
18:51:05 GMT <alexasdasdasd> I setup a REDIS server on AWS and when I connect to it It seems to work, but when i try and type a command I get a connection reset by peer
19:16:13 GMT <spinnix> Send us your config
20:19:39 GMT <codeyman> Is there an upgrade process to follow when I'm moving between redis 2.7 to redis 3.x/4 ?
20:20:17 GMT <codeyman> I'll be moving from 2.8.20 to 3.2.11
20:23:44 GMT <codeyman> Also could someone tell me a stable version for hiredis to use?
20:24:04 GMT <codeyman> is 13.3 good enough? I'll be upgrading from 0.11
20:24:31 GMT <Necrosand> Use the latest release version
20:24:39 GMT <Necrosand> I've used it in several production grade products.
20:28:54 GMT <codeyman> @Necrosand: I don't want to go to redis 4.0, not battle tested yet. Hiredis 13.3 should be fine. Is there a problem with downgrade/upgrade  with using the old rdb files if the customer upgrades/downgrades the redis db?
20:29:09 GMT <codeyman> i.e. downgrade/upgrade between 2.8.20 and 3.2.11
20:29:27 GMT <Necrosand> I was only talking about hiredis
20:30:35 GMT <codeyman> ok
20:30:50 GMT <codeyman> Any idea about upgrading/downgrading redis ?
20:30:55 GMT <Necrosand> I don't know if you will be able to downgrade, I am pretty sure you can upgrade using the rdb's though.
20:31:02 GMT <Necrosand> Definitely test it out and verify your data integrity.
20:31:56 GMT <codeyman> thanks.. yeah, trying it out. Just wondering if I need to give some obvious upgrade scripts to the end user
20:33:19 GMT <Necrosand> https://github.com/antirez/redis/issues/3218 should give you a bit more insight
20:37:12 GMT <codeyman> @Necrosand: Thanks a ton. That answered my queries.
20:37:36 GMT <Necrosand> No problem. May your Redis performance always be quick!
20:41:08 GMT <lberk> anybody here using redis-cluster with kubernetes? was following along with https://github.com/kelseyhightower/kubernetes-redis-cluster, changed the gce storage to emptyDir: {}'s
20:42:01 GMT <lberk> but when running the redis-trib create --replicas 1 step, I provide the cluster ip's defined in the service, but they also come back with ip's used by the host directly
20:42:22 GMT <lberk> so a mix between 172.*.*.* and 10.*.*.* addresses
20:42:31 GMT <lberk> which leaves redis-cli commands (testing the cluster), failing
22:23:21 GMT <im_lost> Hello ! I wonder if this is possible to tell a redis cluster to store hash slot on every node without splitting them by range ?
22:24:09 GMT <im_lost> because while reading the doc it says that for 3 redis cluster machine, one get 1/3 of the hash slot, the second get 1/3 and the third get 1/3 too
22:24:26 GMT <im_lost> is it possible to make available the data for each node ?
22:24:46 GMT <im_lost> thanks for any hint
22:26:26 GMT <im_lost> or the redis cluster didnt provide a way to put data on every node /
22:26:28 GMT <im_lost> ?
23:31:33 GMT <cornfeedhobo> how does one benchmark hmset?
23:44:45 GMT <minus> cornfeedhobo: using redis-benchmark?
23:48:05 GMT <cornfeedhobo> yeah i think i figured it out now
23:49:02 GMT <cornfeedhobo> minus: is it possible to write multiple fields and combine with another test, like lpush or zadd?
23:50:22 GMT <minus> they're all limited to one command afaik, but you might be able to modify the code
23:50:51 GMT <cornfeedhobo> okay. thanks!