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

[Query] Add multi-zonal capability to remote reads #1687

Merged
merged 5 commits into from
Jun 3, 2019

Conversation

arnikola
Copy link
Collaborator

What this PR does / why we need it:

Adds multi-zone capability to remote reads for Query

Special notes for your reviewer:

Does this PR introduce a user-facing and/or backwards incompatible change?:

NONE

Does this PR require updating code package or user-facing documentation?:

NONE

// RemoteListenAddresses is the remote listen addresses to call for remote
// coordinator calls.
// RemoteZones are the configuration settings for remote coordinator zones.
RemoteZones RemoteZones `yaml:"remoteZones"`
Copy link
Collaborator

@robskillington robskillington May 31, 2019

Choose a reason for hiding this comment

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

nit: Can we call this just RemoteClusters? Technically speaking they could be regions instead of zones (if deployed across a region), etc.

Copy link
Collaborator

@robskillington robskillington May 31, 2019

Choose a reason for hiding this comment

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

Second thought, maybe just call it Remotes Remotes 'yaml:"remotes"' and have a type Remote struct instead of type RemoteZone struct

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I gotta be honest and say I couldn't decide on a name for this so I went with RemoteZones because I knew it would be contentious in the PR haha; remotes sounds good

) (storage.Storage, error) {
if len(remoteAddresses) == 0 {
// No addresses; skip.
return nil, nil
Copy link
Collaborator

@robskillington robskillington May 31, 2019

Choose a reason for hiding this comment

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

Hm, perhaps make this an error? This would be a very strange config to call "valid" and might end up with unintended mistakes in config that is hard to debug.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

So this is a "valid" case, where act as a server to remote zones but are not connected as a client (maybe a case for setting up dedicated servers to host cross zone traffic or something like that)

Copy link
Collaborator

@robskillington robskillington left a comment

Choose a reason for hiding this comment

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

Looking good other than comments

@codecov
Copy link

codecov bot commented Jun 3, 2019

Codecov Report

Merging #1687 into master will decrease coverage by <.1%.
The diff coverage is 61.1%.

Impacted file tree graph

@@           Coverage Diff            @@
##           master   #1687     +/-   ##
========================================
- Coverage    71.9%   71.8%   -0.1%     
========================================
  Files         970     970             
  Lines       81364   81324     -40     
========================================
- Hits        58503   58456     -47     
- Misses      19016   19028     +12     
+ Partials     3845    3840      -5
Flag Coverage Δ
#aggregator 82.4% <ø> (ø) ⬆️
#cluster 85.7% <ø> (ø) ⬆️
#collector 63.9% <ø> (ø) ⬆️
#dbnode 79.9% <ø> (-0.1%) ⬇️
#m3em 73.2% <ø> (ø) ⬆️
#m3ninx 74.1% <ø> (ø) ⬆️
#m3nsch 51.1% <ø> (ø) ⬆️
#metrics 17.6% <ø> (ø) ⬆️
#msg 74.7% <ø> (ø) ⬆️
#query 66.3% <61.1%> (-0.1%) ⬇️
#x 85.7% <ø> (-0.1%) ⬇️

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 83d0a46...fc12e4b. Read the comment docs.

@arnikola arnikola merged commit c0d102f into master Jun 3, 2019
@arnikola arnikola deleted the arnikola/multi-zone-coordinator branch June 3, 2019 16:37
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