05:10:46 GMT hi 05:10:49 GMT anyone here 05:10:57 GMT i have a question 05:13:21 GMT u.... 05:16:43 GMT Having questions is good, asking them is better if you want them answered 05:20:49 GMT i have used for redis-stat for monitoring 05:21:03 GMT there are lots of indicator for monitoring 05:23:21 GMT but i have to know the indicators that will be make problems 05:24:38 GMT but there is no Criterions excepting cpu memory disk 05:25:48 GMT could you anybody to inform the creterions for indecator which will make problems .. 05:26:24 GMT sorry i don't know english very well.. 05:26:30 GMT please let me know it 05:31:41 GMT i did redis cluster yesterday 05:31:46 GMT no sweat 05:32:02 GMT alot easier than mysql cluster 14:54:25 GMT hi all, I'm running redis 3.07, I've noticed that in my dev environment, connections to my sentinel nodes timeout maybe 10% of the time (this does not happen in my stage env running 3.05) 14:54:29 GMT any ideas on what to look at? 14:54:49 GMT one bit of info is that the dev env might have many more connections than the stage node at one time 14:55:59 GMT to test, i do a ping with a 1 second timeout to each sentinel 15:30:59 GMT i think it was a maxclients problem, i just made sure maxclients was 10000 and it seems fine so far 15:51:11 GMT hello 15:51:16 GMT where I can read more about the way Redis stores keys? 15:51:23 GMT i want to use prefix scans (server-*), but not sure if it's a right idea to do with redis 15:51:27 GMT other storages like HBase/BigTable store keys in sorted order, so it's a relatively fast operation 15:51:31 GMT if you e.g. want 1000 keys starting with prefix server-0- and ending with server-1- 18:00:26 GMT just to be sure: with the python lib's pubsub().listen(), is there a chance of missing messages if the handler function takes too long? 18:00:42 GMT shodan45: no 18:00:54 GMT minus: thanks 18:01:09 GMT if you handler is constantly too slow you run into the risk of the buffer filling up though 18:01:57 GMT minus: ok, understood