Skip to content

[improvement]Randomly get a new BE address when writing one batch at a time #59

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
merged 1 commit into from
Dec 20, 2022

Conversation

lexluo09
Copy link
Contributor

@lexluo09 lexluo09 commented Dec 14, 2022

Proposed changes

reduce the Coordinator BE load pressure

  1. The BE address remains the same until the write fails. Improve cluster load balancing.
  2. The Coordinator BE receiving data and distributing data to other data nodes. It receives more network traffic than other nodes.

Problem Summary:

Describe the overview of changes.

  1. The BE nodes collection is cached and refresh periodically.
  2. Randomly get a new BE address from cache when writing one batch at a time.

Checklist(Required)

  1. Does it affect the original behavior: (Yes/No/I Don't know)
  2. Has unit tests been added: (Yes/No/No Need)
  3. Has document been added or modified: (Yes/No/No Need)
  4. Does it need to update dependencies: (Yes/No)
  5. Are there any changes that cannot be rolled back: (Yes/No)

Further comments

@lexluo09
Copy link
Contributor Author

@hf200012 would you mind take a look?

Copy link
Contributor

@hf200012 hf200012 left a comment

Choose a reason for hiding this comment

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

LGTM

@hf200012 hf200012 merged commit b797bfc into apache:master Dec 20, 2022
@lexluo09 lexluo09 deleted the optimize_get_be branch December 20, 2022 07:02
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.

None yet

2 participants