"Douglas K. Rand" <[email protected]> writes:
> I'm running into Postgres' default 100 maximum connection limit with a
> director that has maximum concurrent jobs set to 10. I could increase
> the Postgres maximum, but the number of connections for the number of
> jobs seems off.
first, thank you pointing out this setting in PostgreSQL! that may
explain some of the intermittent issues I have been having, since I have
director concurrency set to exactly 100 ...
is your director max concurrency really set to 10 in the Director
section?
> It seems that when a large batch of jobs are scheduled to start at the
> same time that there is a spike in the number of Postgres connections,
> even though the bulk of those jobs are simply waiting to run.
>
> How many available Postgres connections do I need for each Bareos job?
on my server, it seems to be 1 connection per running job, as expected
("running" includes waiting for storage in this case). you are using
attribute spooling, I assume?
> The Postgres database is dedicated to Bareos, it has no other
> connections. And Postgres is running on the same host as the director.
>
> Any thoughts?
how many jobs are listed in "status sd" ?
--
Kjetil T. Homme
Redpill Linpro AS - Changing the game
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
