Skip to content

Adjust initial gen_server_call_timeout #3232

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

Merged

Conversation

britto
Copy link
Contributor

@britto britto commented Jul 26, 2021

Proposed Changes

Preventing amqp_connection:start/2 from logging a warning when we use default values.

The default for connection_timeout is already 60000. When we don't explicitly set it to a lower value, amqp_connection:maybe_update_call_timeout/2 adjusts it to 70000 and logs a warning message (See #2660), which may appear unexpected, especially for users upgrading to 3.8.10+ with no config changes.

This change addresses that problem by pre-adjusting it to 70000, making it safe by default and ensuring our default values don't conflict with each other.

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)

Checklist

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Further Comments

An alternative approach to this would be reducing the original connection_timeout default to 50000 for example, but that could potentially be a change of bigger impact, since 60000 has been the default since 1905e30. Please let me know if this is a saner approach and I can make the changes.

to prevent `amqp_connection:start/2` from logging a warning when we use default
values.

The default for `connection_timeout` is already 60000. When we don't explicitly
set it to a lower value, `amqp_connection:maybe_update_call_timeout/2` adjusts
it to 70000 and logs a warning message, which may appear unexpected, especially
for users upgrading to 3.8.10+ with no config changes.

This change addresses that problem by pre-adjusting it to 70000, making it safe
by default and ensuring our default values don't conflict with each other.
@michaelklishin michaelklishin merged commit 8288bab into rabbitmq:master Jul 26, 2021
michaelklishin added a commit that referenced this pull request Jul 26, 2021
…imeout

Adjust initial gen_server_call_timeout

(cherry picked from commit 8288bab)
@michaelklishin
Copy link
Collaborator

Backported to v3.9.x.

michaelklishin added a commit that referenced this pull request Jul 26, 2021
…imeout

Adjust initial gen_server_call_timeout

(cherry picked from commit 8288bab)
@michaelklishin
Copy link
Collaborator

Backported to v3.8.x.

@michaelklishin michaelklishin added this to the 3.8.20 milestone Jul 26, 2021
@britto britto deleted the adjust-initial-gen-server-call-timeout branch July 26, 2021 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants