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.

Sign up for GitHub

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

Jump to bottom

[Improve] Optimize the HeartbeatMsg class #8391

Closed
2 tasks done
gosonzhang opened this issue Jul 3, 2023 · 4 comments
Closed
2 tasks done

[Improve] Optimize the HeartbeatMsg class #8391

gosonzhang opened this issue Jul 3, 2023 · 4 comments
Assignees
@gosonzhang @fuweng11
Labels
component/dataproxy component/manager type/improve
Milestone
1.11.0

Comments

@gosonzhang
Copy link
Contributor

Description

In the previous improvement[1], it was mentioned that for the DataProxy node, the reported heartbeat information contains multiple sources, each source has a separate {ip, port, protocolType} information pair, and other information is the same, so the report information of DataProxy needs to be carried in a List for this part, instead of a comma-separated field string, which is not easy to expand.

  1. [Improve][DataProxy] Adjust the source report information acquisition source #6234

InLong Component

InLong DataProxy

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct
@gosonzhang gosonzhang added this to the 1.8.0 milestone Jul 3, 2023
This was referenced Jul 3, 2023
Closed
Closed
@gosonzhang gosonzhang modified the milestones: 1.8.0, 1.9.0 Jul 3, 2023
@github-actions
Copy link

github-actions bot commented Sep 2, 2023

This issue is stale because it has been open for 60 days with no activity.

@github-actions github-actions bot added the stage/stale Issues or PRs that had no activity for a long time label Sep 2, 2023
@dockerzhang dockerzhang modified the milestones: 1.9.0, 1.10.0 Sep 14, 2023
@github-actions github-actions bot removed the stage/stale Issues or PRs that had no activity for a long time label Sep 15, 2023
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 60 days with no activity.

@github-actions github-actions bot added the stage/stale Issues or PRs that had no activity for a long time label Nov 14, 2023
@dockerzhang dockerzhang modified the milestones: 1.10.0, 1.11.0 Dec 5, 2023
@github-actions github-actions bot removed the stage/stale Issues or PRs that had no activity for a long time label Dec 6, 2023
@gosonzhang
Copy link
Contributor Author

Since the implementation of #9512 has been completed, modifications to this issue will now begin.

@gosonzhang
Copy link
Contributor Author

finished

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

@gosonzhang gosonzhang

@fuweng11 fuweng11

Labels
component/dataproxy component/manager type/improve
Projects
None yet
Milestone
1.11.0
Development

No branches or pull requests
3 participants
@gosonzhang @dockerzhang @fuweng11