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

META does not properly handle E_RETRY_EXHAUSTED error codes #6022

Closed
Datebasesystem opened this issue Apr 3, 2025 · 0 comments
Closed

META does not properly handle E_RETRY_EXHAUSTED error codes #6022

Datebasesystem opened this issue Apr 3, 2025 · 0 comments
Labels
affects/none PR/issue: this bug affects none version. process/fixed Process of bug severity/none Severity of bug type/bug Type: something is unexpected

Comments

@Datebasesystem
Copy link

Please check the FAQ documentation before raising an issue

Describe the bug (required)

During the process of balancing data, META will keep asking STORAGE LEADER whether catch up data is complete. When the amount of data is relatively large, the storage transfers data for a long time, which may time out and return an error code to the leader E_RETRY_EXHAUSTED. At this time, the leader does not ask the current storage (that is, raft leader) for the progress of caatch up again, but asks the next hosts in the raft group. So there is one more invalid request.

Your Environments (required)

  • OS: Linux
  • Compiler: g++ (GCC) 8.5.0
  • CPU: x86_64
  • Commit id (e.g. a3ffc7d8)

How To Reproduce(required)

Steps to reproduce the behavior:

  1. Step 1
  2. Step 2
  3. Step 3

Expected behavior

Additional context

Here the meta is for E_RETRY_EXHAUSTED error code, and should be retried directly on the current raft leader, not other hosts.

@Datebasesystem Datebasesystem added the type/bug Type: something is unexpected label Apr 3, 2025
@github-actions github-actions bot added affects/none PR/issue: this bug affects none version. severity/none Severity of bug labels Apr 3, 2025
@github-actions github-actions bot added the process/fixed Process of bug label Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/none PR/issue: this bug affects none version. process/fixed Process of bug severity/none Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

1 participant