Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many client connections (postgres) #462

Open
titus-anromedonn opened this issue Jul 1, 2023 · 0 comments
Open

Too many client connections (postgres) #462

titus-anromedonn opened this issue Jul 1, 2023 · 0 comments
Labels

Comments

@titus-anromedonn
Copy link

Bug

When running with threads >= 64 postgres dies during imports due to too many client connections at various stages. I recommend that the postgres config gets updated to something like 512 or 1024 max connections just to be safe.

The first time I ran with 128 threads the image didn't make it past trying to load the ranks. It finished loading in the flat node file and died.

I ran it a second time with 64 threads and it failed again when importing the tiger data due to the same issue,. Unlike last time though it just sat there without actually proceeding.

Resolution

I manually went in, changed the max connections parameter, restarted postgres and imported everything else manually. Everything worked fine after that.

Desktop

  • OS & Version: [Ubuntu 22.04]
  • Docker Version: [e.g. 20.10.18]
  • Nominatim Version: 4.2.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant