zydronium/google-nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus.git synced 2025-07-06 11:13:35 +02:00
Code Issues Projects Releases Packages Wiki Activity

Closing the bug regarding Cloud SQL connection configs (#1012)

Browse source 
* Add comments to Cloud SQL configs

I believe the similarity in trace to https://github.com/brettwooldridge/HikariCP/issues/1212
is misleading.

The real cause of the exceptions may be that we ran out of connections. At the
time, the production Cloud SQL server could handle 500 connections at the
maximum. That number was within reach of a busy Nomulus server.

The maximum connection in production has been increased to 1000. We
haven't encountered this issue for a long time. All connection problems
are due to Cloud SQL maintenance or other GCP related issues.

This issue is tracked by b/154720215, which is being closed with this
PR.
This commit is contained in:
Weimin Yu 2021-03-16 10:29:30 -04:00 • committed by GitHub
parent 58e561704c
commit bae5dacbae
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

19
core/src/main/java/google/registry/config/files/default-config.yaml
View file

@ -207,18 +207,13 @@ hibernate:
# Connection pool configurations. # Connection pool configurations.
hikariConnectionTimeout: 20000 hikariConnectionTimeout: 20000
# We occasionally received "Connection is not available, request timed out" # Cloud SQL connections are a relatively scarce resource (maximum is 1000 as
# exception when setting minimumIdle to 0 and it turned out it is a bug (See # of March 2021). The minimumIdle should be a small value so that machines may
# https://github.com/brettwooldridge/HikariCP/issues/1212) in HikariCP. # release connections after a demand spike. The maximumPoolSize is set to 10
# # because that is the maximum number of concurrent requests a Nomulus server
# We tried to use a fixed size pool but ran into an issue(See b/155383029), # instance can handle (as limited by AppEngine for basic/manual scaling). Note
# so we need further investigation to figure out the proper size of the pool. # that BEAM pipelines are not subject to the maximumPoolSize value defined
# # here. See PersistenceModule.java for more information.
# HikariCP also recommends not setting minimumIdle for maximum performance
# and responsiveness to spike demands (See
# https://github.com/brettwooldridge/HikariCP).
#
# TODO(b/154720215): Investigate the long term fix.
hikariMinimumIdle: 1 hikariMinimumIdle: 1
hikariMaximumPoolSize: 10 hikariMaximumPoolSize: 10
hikariIdleTimeout: 300000 hikariIdleTimeout: 300000