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

[INLONG-9867][Manager] Unified configuration process for standalone and sortflink #9868

Merged
merged 12 commits into from May 6, 2024

Conversation

fuweng11
Copy link
Contributor

@fuweng11 fuweng11 commented Mar 23, 2024

Prepare a Pull Request

Motivation

Unified configuration process for standalone and sortflink.
The current configuration process of standalone has the following issues:

  1. Configuration changes will be updated in real-time to the manager's cache. Once a configuration change occurs, sortstandalone will sense it and write data based on the new configuration.
    Once the configuration is modified incorrectly, it can lead to issues with the entire write.

  2. The configuration in the manager cache is to fully pull the content from the database and filter it. Each refresh requires a full database query and repeated filtering operations at the service layer.

  3. There is no management function for whether each configuration is functioning properly. Once the configuration is registered on the manager side, it defaults to the correct configuration.
    Failure to verify and issue each configuration results in unreliable configurations.

Modifications

The flowchart of standalone pull configuration is as follows:
image

The getClusterConfigV2 interface has been set up, where the data comes from the sort_config table, which can only be obtained through workflow configuration operations. The interface protocol is consistent with the getClusterConfig interface.

  1. Incorporate the configuration process of sort standalone into the manager's configuration management system and add a configuration information table. The JSON format configuration information that sort standalone needs to pull will be saved in a field of this table. Only those that are successfully configured will be recorded in this table.

  2. Modify the configuration timer to be pulled to the cache and change it to actively trigger the configuration update cache. After successful configuration, the configuration information will be registered in this configuration information table, loaded into the cache, and the md5 value will be modified.

@fuweng11 fuweng11 marked this pull request as draft March 23, 2024 11:13
@fuweng11 fuweng11 marked this pull request as ready for review March 23, 2024 12:39
aloyszhang
aloyszhang previously approved these changes Mar 25, 2024
@fuweng11 fuweng11 marked this pull request as draft March 25, 2024 09:24
@fuweng11 fuweng11 marked this pull request as ready for review April 17, 2024 10:41
aloyszhang
aloyszhang previously approved these changes Apr 17, 2024
@fuweng11 fuweng11 marked this pull request as draft April 17, 2024 12:33
@fuweng11 fuweng11 marked this pull request as ready for review April 23, 2024 08:26
aloyszhang
aloyszhang previously approved these changes Apr 23, 2024
Copy link
Contributor

@vernedeng vernedeng left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Contributor

@aloyszhang aloyszhang left a comment

Choose a reason for hiding this comment

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

LGTM

@dockerzhang dockerzhang merged commit 22d6859 into apache:master May 6, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Improve][Manager] Unified configuration process for standalone and sortflink
5 participants