- You'll need to share the same redis password across several
projects.
Redis does have users and permissions, at least from a quick look at
their docs:
https://docs.redis.com/latest/rc/security/database-security/passwords-use...
- Since you'll use an emptyDir (in-memory storage), every restart
will flush the cache for all connected applications.
I was thinking of running Redis in a VM, not in OpenShift. Sorry if
that wasn't clear in my initial message.
- Applications owners lose control over the redis instance in case
they want to do some fancy stuff with it, or just general debugging.
True.
It avoids a single point of failure for a bunch of services.
Right, but that's what our PostgreSQL host is at the moment already.
Contention/resource problems. (ie, one app is hammering the shared
instance and starving other apps for resources).
True, true.
OK, that makes sense. The good thing about having a central Redis DB
was, in my mind, to have persistent storage. What happens if I store a
lot of data in the Redis Openshift pod? Won't that hit a memory limit?
I think our current usage of Redis has been pubsub and light cache,
but we haven't stored a lot of data in there yet.
Le lun. 28 nov. 2022 à 01:17, Kevin Fenzi <kevin(a)scrye.com> a écrit :
>
> On Thu, Nov 24, 2022 at 10:56:57AM +0100, Aurelien Bompard wrote:
> > Hey folks!
> >
> > The new version of FMN will run in OpenShift and will use Redis as a
> > cache backends (we chose it over memcached because it can do native
> > "is-this-string-in-this-set" operations).
> >
> > I can deploy redis inside my openshift project easily enough , but I
> > was wondering if it would be worthwhile to have a shared Redis
> > instance, like we have a shared PostgreSQL instance.
> > It's not just for ease of use, but I expect to store quite a bit of
> > data in our Redis instance, and since we don't attach persistent
> > storage to OpenShift that means that it will live in the pod's memory.
> > So I'm being conscious of the memory hog it can become.
> > Unless I'm mistaken there can be several databases in the same Redis
> > instance, so we could share it between projects without stepping on
> > each other's toes.
> >
> > What do you think?
>
> We have talked about it before, but I think the tradeoffs come down on
> the side of seperate instances. They aren't too hard to spin up in
> openshift.
>
It avoids a single point of failure for a bunch of services.
>
> Contention/resource problems. (ie, one app is hammering the shared
> instance and starving other apps for resources).
>
> etc.
>
> So, I would say we should do seperate ones per service...
>
> kevin
> _______________________________________________
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
> Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue