07:28:29 GMT <joe___> HELP
11:17:30 GMT <badboy_> mfilipe: redisCommand is synchronous and will already give you the reply
11:18:04 GMT <badboy_> if you use redisAppendCommand you then have to use redisGetReply to get the response,
12:15:20 GMT <colo-work> hi there
12:16:09 GMT <colo-work> we have a redis instance that's been fed with data for several years, and noone _really_ knows what the actually useful sub-set of the data in it might be :)
12:16:29 GMT <colo-work> is there any tooling available to help determine very, very cold keys?
12:31:51 GMT <mfilipe> badboy_, i believe i solve my problem (need more tests) using the concept of pipelining from https://github.com/redis/hiredis
12:32:48 GMT <badboy_> colo-work: FLUSHALL and see who complains?
12:35:47 GMT <mfilipe> no, it doesnt work :(
12:38:09 GMT <mfilipe> i'm sending a big json (5kb) to a key and after i publish an event in a channel informing about the new json in that key... the problem is that when the other component reads the event and try to get the value key in redis, the key is not available yet. how could I fix this?
12:38:47 GMT <mfilipe> i'm looking for a solution in the component which sends the big json
12:39:17 GMT <mfilipe> it has to confirm if the key was inserted
14:21:50 GMT <colo-work> badboy_, yeah, I wish that were possible ;)
16:45:25 GMT <slappyjam> Hey guys!  I have a question I hope you can help with.  We are running redis 3.2.6 and are seeing some latency issues with our cluster.
16:45:46 GMT <slappyjam> our application requires latency <10ms and we get
16:45:56 GMT <slappyjam> root@ewr-idm-x3:~# redis-cli --latency-history -p 7000
16:45:57 GMT <slappyjam> min: 0, max: 24, avg: 0.11 (1476 samples) -- 15.01 seconds range
16:46:19 GMT <slappyjam> my thought was that we need to add more redis nodes to our cluster
16:46:33 GMT <slappyjam> as the current nodes are too busy to respond fully in <10ms
16:46:47 GMT <slappyjam> we have 4 machines each machine running 12 redis-server processes
16:47:00 GMT <slappyjam> each redis process only uses one core, correct?
16:47:06 GMT <slappyjam> we have bgsave turned off for now
16:48:45 GMT <slappyjam> thoughts?
16:51:50 GMT <slappyjam> no love today, I guess
17:09:35 GMT <slappyjam> Does redis only use one thread for both reads and writes?
20:56:54 GMT <ee> is there any security best practices documentation available?
20:57:04 GMT <ee> a default config maybe thats out there? etc
20:58:57 GMT <ee> something like: must use tls for all connections, must use auth, run as low priv user, etc
20:59:35 GMT <ee> looking for a safe way to deploy this out to an enterprise and im not overtly familiar with the application/service