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

Add configurable warm up for remote datacenter connections #1198

Merged
merged 2 commits into from
Jun 20, 2019

Conversation

cgtz
Copy link
Contributor

@cgtz cgtz commented Jun 20, 2019

Previously, only local datacenter connections could be prewarmed in the
router. This adds a new config to allow prewarming remote datacenter
connections. This could be useful in deployments where cross-DC requests
are likely.

Previously, only local datacenter connections could be prewarmed in the
router. This adds a new config to allow prewarming remote datacenter
connections. This could be useful in deployments where cross-DC requests
are likely.
@cgtz cgtz requested a review from zzmao June 20, 2019 00:22
@codecov-io
Copy link

codecov-io commented Jun 20, 2019

Codecov Report

Merging #1198 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master    #1198   +/-   ##
=========================================
  Coverage     83.62%   83.62%           
  Complexity       57       57           
=========================================
  Files             6        6           
  Lines           348      348           
  Branches         38       38           
=========================================
  Hits            291      291           
  Misses           45       45           
  Partials         12       12

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8e2c5a1...7044b18. Read the comment docs.

Copy link
Contributor

@zzmao zzmao left a comment

Choose a reason for hiding this comment

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

LGTM.

@cgtz cgtz requested a review from ankagrawal June 20, 2019 16:19

/**
* The percentage of {@link RouterConfig#routerScalingUnitMaxConnectionsPerPortSsl} or
* {@link RouterConfig#routerScalingUnitMaxConnectionsPerPortPlainText} to warm up for data nodes in the local
Copy link
Collaborator

Choose a reason for hiding this comment

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

The comments for routerConnectionsRemoteDcWarmUpPercentage need to be changed perhaps!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed!

routerConnectionsLocalDcWarmUpPercentage =
verifiableProperties.getIntInRange("router.connections.local.dc.warm.up.percentage", 25, 0, 100);
routerConnectionsRemoteDcWarmUpPercentage =
verifiableProperties.getIntInRange("router.connections.remote.dc.warm.up.percentage", 0, 0, 100);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should the default value be 25 here? We are setting default in the declaration decorator to 25.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ah thanks for catching that. The default should be 0 since I feel that warming up cross DC connections only applies to specific ambry use cases, but I will fix the decorator.

Copy link
Collaborator

@ankagrawal ankagrawal left a comment

Choose a reason for hiding this comment

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

LGTM!

@ankagrawal ankagrawal merged commit cf53025 into linkedin:master Jun 20, 2019
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.

4 participants