04:19:05 GMT <Sparrow_> hi, i am using redis through jedis and getting the error "redis.clients.jedis.exceptions.JedisDataException: EXECABORT Transaction discarded because of previous errors."
04:19:39 GMT <Sparrow_> i am not running out of memory..
04:19:50 GMT <Sparrow_> what is the possible cause?
04:21:06 GMT <Sparrow_> fyi: redis_version:3.2.3 please help
04:54:50 GMT <minus> Not enough info; what are you trying to do?
07:18:56 GMT <ashu2394> hello
07:20:08 GMT <ashu2394> I had a question whether we can get number of masters in sharded redis cluster stored
07:34:51 GMT <badboy_> ashu2394: I don't understand your question
07:40:32 GMT <ashu2394_> In a redis cluster can we get number of masters supposed to be there
07:40:36 GMT <ashu2394_> ?
07:46:16 GMT <badboy_> sure
07:46:49 GMT <badboy_> CLUTER INFO
07:46:49 GMT <badboy_> cluster_known_nodes:6
07:46:49 GMT <badboy_> cluster_size:3
07:53:51 GMT <ashu2394_> so the cluster size is number of master
07:55:37 GMT <badboy_> yes
07:55:52 GMT <ashu2394_> but what if one of the masters goes down
07:56:03 GMT <ashu2394_> will show the same information
07:56:05 GMT <ashu2394_> ?
07:58:30 GMT <ashu2394_> I wanted to know if there's any way to connect to one of masters through redis-cli
08:09:46 GMT <badboy_> the known size will stay the same
08:10:00 GMT <badboy_> if a master goes down, it is just considered down, but still belongs to the cluster
08:10:06 GMT <badboy_> I don't get your other question either
08:10:16 GMT <badboy_> redis-cli can of course be used to connect to any node
08:22:00 GMT <ashu2394_> but we need the ip of the particular host right ?
08:28:28 GMT <ashu2394_> but if one of the masters goes down we don't have the ip
08:28:37 GMT <ashu2394_> to connect to
08:42:13 GMT <badboy_> thaen connect to another
08:42:35 GMT <badboy_> it's always best to know 3 node addresses and randomly connect to one
08:42:47 GMT <badboy_> if you got a smart client lib that lib than should do the right thing for you anyway
08:44:08 GMT <ashu2394_> One more question : In cluster info
08:44:38 GMT <ashu2394_> what will be cluster size if one of the nodes is down
08:44:40 GMT <ashu2394_> ?
08:46:11 GMT <badboy_> it will stay the same, as I already answered
09:10:14 GMT <nikow> Redis, you are so awesome piece of technology.
09:10:16 GMT <nikow> BUT
09:10:28 GMT <nikow> Can i set maxmemory per db/namespace?
09:10:37 GMT <nikow> Or i need to create second redis instance?
09:12:46 GMT <minus> latter
13:03:14 GMT <jr123> am i correct in assuming that one could not count on results being atomic with redis cluster? the slaves that some queries read from could still be in the progress of getting the latest updates pushed down to them from master? i'm thinking in terms of a simple operation like INCR
22:54:57 GMT <tmberg> Hm.. bttracker "hates" redis now adays. :(
22:57:32 GMT <cbgbt> tmberg: I think I'm missing context. What do you mean?
23:00:11 GMT <tmberg> cbgbt: Oh. Heh. https://github.com/danielfm/bttracker
23:01:04 GMT <tmberg> cbgbt: No hits. No data. Nothing.
23:04:15 GMT <*> tmberg  confused..
23:07:43 GMT <tmberg> Something must have been changed.
23:07:48 GMT <tmberg> https://www.starka.st/run/shm/bandwidth/tmberg/redis-cliINFO.txt
23:09:23 GMT <tmberg> Or its optimized as hell since it doesnt use any cpu resources.