[Improve][SDK] Fix non-atomic worker selection in getWorker in the DataProxy Go SDK

Open
#12,198 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
backend

Research direction

Locate getWorker in the Dataproxy Go SDK and trace how concurrent Send calls choose a worker. Reproduce the behavior with concurrent sends, then verify that worker selection is atomic and distributes calls evenly under high concurrency.

Written by the indexing model from the issue text.

Description

type/improve
Description

In the Dataproxy Go SDK, concurrent Send calls can start the round-robin scan from the same worker index, so the load is not evenly distributed across workers under high concurrency.

InLong Component

InLong SDK

Are you willing to submit PR?
  • Yes, I am willing to submit a PR!
Code of Conduct
Dominant language
Java
Stars
1.5k
Forks
572
Avg merge
12h 52m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/inlong

All issues in apache/inlong

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.