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

[feat][DVO-212] Make memcached client timeout configurable #337

Conversation

0x416e746f6e
Copy link
Contributor

📝 Summary

Use MEMCACHED_CLIENT_TIMEOUT_MS env var to configure the timeout for memcached client.

⛱ Motivation and Context

The default value of 100ms for memcached client timeout might not always be sufficient.

Therefore, we would like to be able to fine-tune this parameter via environment var.


✅ I have run these commands

  • make lint
  • make test-race
  • go mod tidy
  • I have seen and agree to CONTRIBUTING.md

@codecov-commenter
Copy link

Codecov Report

Merging #337 (2752a68) into main (84a9439) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##             main     #337      +/-   ##
==========================================
- Coverage   17.90%   17.89%   -0.01%     
==========================================
  Files          20       20              
  Lines        3743     3745       +2     
==========================================
  Hits          670      670              
- Misses       2990     2992       +2     
  Partials       83       83              
Flag Coverage Δ
unittests 17.89% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
datastore/memcached.go 0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

The default value of `100ms` for `memcached` client timeout might
not always be sufficient.

Therefore, we would like to be able to fine-tune this parameter via
environment var.
@0x416e746f6e 0x416e746f6e force-pushed the feature/dvo-212-investigate-memcached-connection-issues branch from 2752a68 to 650be2e Compare April 7, 2023 09:09
@metachris
Copy link
Collaborator

That's great, thanks! Could you please rebase on latest main?

@metachris
Copy link
Collaborator

btw, i think this is missing the MEMCACHED_CLIENT_TIMEOUT_MS env var to configure the timeout!

@metachris metachris mentioned this pull request Apr 9, 2023
4 tasks
@metachris
Copy link
Collaborator

replaced by #341 because if urgency

@metachris metachris closed this Apr 9, 2023
@metachris metachris deleted the feature/dvo-212-investigate-memcached-connection-issues branch May 25, 2023 07:29
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.

3 participants