"configure resources" is to create and update repos, remote, pub, and distribution. We compare them with a predefined input file and update pulp accordingly. I will try increasing the worker to 10 to see how it goes.
From: mdell...@redhat.com At: 07/23/21 10:22:56 UTC-4:00To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] pulp 3.7.2 api 499 error It will sure help availability. It will not so much help with the syncs (as those are between the workers and the database). I am unsure about what "configure resources" means, but if you are also querying the status of the sync tasks regularly, more api-workers should help, too. On Fri, Jul 23, 2021 at 4:15 PM Bin Li (BLOOMBERG/ 120 PARK) <bli...@bloomberg.net> wrote: > > Our monitoring service watches the /pulp/api/v3/status to alert in case server(3.7.2) is down. We have recently experienced 499 error when the server is busy to configure resources and sync a few hundreds upstream repos. I noticed the pulpcore-api only has 1 worker by default. Will increasing the pulpcore-api workers help in this case? > _______________________________________________ > 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
