Skip to content
This repository was archived by the owner on Jul 10, 2021. It is now read-only.

Conversation

@clanesf
Copy link
Contributor

@clanesf clanesf commented Jun 18, 2020

While going through some recent database troubleshooting, it came to my attention that the property connectionTimeout on this page should actually be connectionTimeoutMs.

Using just connectionTimeout does not work which is only noticable if you are trying to increase the timeout because you are hitting it and realize that adjusting this value doesn't do anything. Correcting this in case anyone else runs into similar scaling issues and needs to be able to adjust this value.

Property names are taken from https://github.com/spinnaker/kork/blob/master/kork-sql/src/main/kotlin/com/netflix/spinnaker/kork/sql/config/ConnectionPoolProperties.kt

It's also correct on the page https://github.com/spinnaker/orca/blob/7c4d3ceece4063dc62e46913b62da67dfddd452b/orca-peering/README.md#operating-notes but somehow it was overlooked here.

@dorbin dorbin requested a review from robzienert June 18, 2020 20:13
connectionTimeout: 5000
connectionTimeoutMs: 5000
maxLifetimeMs: 30000
maxLifetime: 30000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you're missing the removal of maxLifetime.

@robzienert
Copy link
Member

Looks great after the comment is fixed. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants