00:33:47 GMT <levansj01> Hey, I'm trying to access my redis server from another machine but it doesn't work, can someone help me?
00:37:35 GMT <levansj01> I have tried bind 0.0.0.0 but it I'm still getting a connection timeout
05:31:40 GMT <Inge-> you can access it locally? is it blocked by the firewall?
08:07:37 GMT <StefanS_> Hi everyone, I have an architectural question. I have 11 web servers, all identical with a proxy load balancer in front. I would like to add redis to each one of these web servers however I am unsure about what would be the best setup. How many slaves? how many masters? Sentinel?
08:08:10 GMT <StefanS_> I am also running an ElasticSearch cluster across those 11.
08:19:12 GMT <StefanS_> Is it wrong to run a slave and master on the same machine?
09:46:42 GMT <minus> StefanS_: if a single machine is large enough to host its own, private instance of redis and you don't care if it's wiped (shouldn't happen though), then don't do any sentinel/clustering. that's the least complex way and thus preferrable. if you want to spread your data over all instances, use cluster (optionally with redundancy). running master and slave(s) of a sentinel setup on the same box is completely
09:46:45 GMT <minus> pointless
09:50:41 GMT <michel_v> yeah the usual thing that will happen is that the machine will go unresponsive, instead of just one instance
09:50:55 GMT <michel_v> so both fall at the same time, and nothing good has been achieved
10:21:22 GMT <StefanS_> ok, thanks
11:46:00 GMT <gitgud> hi. if i use a database that supports caching do i still need to use redis ?
11:47:12 GMT <xiaomiao> depends
11:47:31 GMT <gitgud> if they are both caching
11:47:52 GMT <gitgud> could you give me a case where redis caching + rdbms is important?
11:47:59 GMT <gitgud> both caching
11:48:58 GMT <xiaomiao> depends on what you are caching
11:49:18 GMT <xiaomiao> for example - simple webapp, caching DB queries vs. caching HTML fragments
11:49:56 GMT <gitgud> i have big datasets im returning to customers
11:50:03 GMT <gitgud> and i just heard mongodb has its internal caching
11:51:01 GMT <xiaomiao> I would strongly recommend not using mongodb
11:51:19 GMT <xiaomiao> well, if in doubt do some benchmarking to see what the performance impact of caching is
11:51:19 GMT <gitgud> why do you say so?
11:51:34 GMT <xiaomiao> eh, it has a history of not persisting data, and it's all in all kinda slow
12:13:41 GMT <minus> if mongodb is acceptable for you use case you can use it of course. in my experience it's been somewhat slow, but we were using it more as a key-value store. i don't know anything about how good or bad it deals with data loss
12:15:04 GMT <minus> if performance isn't a problem or if you can optimize your rdbms or the way you query data from it well enough, i'd avoid adding caching, because it's additional complexity and management overhead