00:10:36 GMT <hydraulix> Hi, is there a BI tool that can interface with Redis? For example, something like Qlik or Tableau?
06:57:24 GMT <Inge-> Salvatore is in .it? I thought he was in like, Brazil
09:57:02 GMT <dudeji> Hi does master-slave concept is old now and usualy peer to peer clustering being done along with replication and does redis has support for peer to peer clustering ?
10:04:29 GMT <cbgbt> dudeji: https://redis.io/topics/cluster-tutorial
10:05:01 GMT <cbgbt> dudeji: there are caveats to clustering, especially if you are using transactions or scripts.
10:05:56 GMT <dudeji> No transaction  strictly key value store.
10:06:11 GMT <cbgbt> Question for you kind folks, I'm using redis-py to implement a transaction that does a large number of conditional writes. Is it possible to pipeline all of the reads, and then pipeline all of the writes after the reads have completed, while watching the same keys throughout?
10:06:59 GMT <cbgbt> dudeji: Redis clustering works by sharding certain keys to certain redis hosts, it isn't like multi-master replication if that's what you're looking for
10:07:43 GMT <cbgbt> But it still works as a way to distribute certain workloads such that writes and reads are more happily distributed
10:08:12 GMT <dudeji> so how will i request for keys ? usually i connect to one hosta nd port then get data from there .  But in sharding mode which port and host will i query ?
10:08:59 GMT <dudeji> and what if i am trying to update some key which is not found in one of server ?
10:10:23 GMT <cbgbt> dudeji: You'll want to take a careful look at the link I showed you. The short version is that your client has a mechanism for knowing which shard to connect to based on the key you are trying to access
10:10:51 GMT <dudeji> ohk
10:16:47 GMT <cbgbt> To circle back on my own question, it seems like Redis disregards WATCHed keys upon EXEC, meaning I can't watch keys for the duration of two MULTI calls, as far as I can tell.
13:11:27 GMT <Denny> hi @all
13:12:20 GMT <Guest84576> May I ask some questions here if I have problems with my redis master/slave replication?
16:04:52 GMT <monobaila> I want to build an alert for slaves that are behind the master (for a yet to be determined threshold/time window), I'd like to double check my understanding: slave byte lag = master_repl_offset - slave_repl_offset (with these offset metrics collected from master and slave node respectively)
16:50:39 GMT <redis_newbie> Hello guys... I'm trying to test failover on a sentinel setup, but seems like when I force master to failover, sentinel promotes the slave, but the new aster still thinks it's a slave?
16:51:03 GMT <redis_newbie> anyone there that can put me in the rigtht direction? thanks!