Hi Martin, Our analytics design requires redis to be running locally (w/ no sentinel, no clustering) on each of the analytics nodes. And as Pedro stated, we do not depend on redis being persistent - data is recreated when we connect to redis.
regards, - Raj On Apr 29, 2015, at 12:23 PM, Martin Loschwitz <m.loschw...@syseleven.de> wrote: > Sorry, > > i just rememberd a discussion Michael Renner recently had with Pedro, in > which Pedro > stated that redis doesn’t have to be persistent anyway. Okay, if that’s the > case, we will > just do away with the idea of sentinel altogether. > > Best regards > Martin > >> Am 29.04.2015 um 21:20 schrieb Martin Loschwitz <m.loschw...@syseleven.de>: >> >> Hallo Raj, >> >> no. We’re running Redis with Sentinel here, and access to Redis is possible >> through an >> HAProxy load balancer that will ensure that nodes always land on the one >> redis node that >> is currently the master of the sentinel cluster. I don’t see how scaling out >> redis for purposes >> of performance and high availability would work in any other way. We’ll need >> the analytics >> api to be fixed to allow to specify an arbitrary ip address to connect to >> redis. Shall I fill a >> bug in Launchpad? >> >> Best regards >> Martin >> >>> Am 29.04.2015 um 21:17 schrieb Raj Reddy <rajre...@juniper.net>: >>> >>> Hi Martin, >>> >>> It appears we are relying on the fact that redis is listening on 0.0.0.0 >>> You can comment the redis.conf bindip parameter or change it to 0.0.0.0 >>> >>> regards, >>> - >>> Raj >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
