I am not sure if the cache invalidations will be pushed to all redis instances if deployed that way. Maybe there is a little bit of extra work needed.
On Mon, Sep 20, 2021 at 10:31 PM Brian Bouterse <bmbou...@redhat.com> wrote: > > I believe with 3.14+ and new style workers, you can have an independant redis > on the backup server. > > With the new-style tasking system (the default in 3.14) you no longer need > Redis for tasking. It's only purpose then is to help speedup the content app > which caches info about requests to make answering subsequent content-app > requests easier. If those caches miss, e.g. if you had a failover event, Pulp > will continue to work fine, just building the Redis cache data as it goes. > > On Mon, Sep 20, 2021 at 4:22 PM Bin Li (BLOOMBERG/ 120 PARK) > <bli...@bloomberg.net> wrote: >> >> We configured a redis slave on a passive backup server which shares the same >> external database with the primary pulp server. I noticed the task queues >> are now being tracked in the database. Is it still necessary to configure >> redis as a slave or we can have an independent instance of redis on the >> backup server? >> >> Thanks >> _______________________________________________ >> Pulp-list mailing list >> Pulp-list@redhat.com >> https://listman.redhat.com/mailman/listinfo/pulp-list > > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://listman.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list
