Skip to content

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

Description

@yfsn666

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions