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

feat(horaemeta): add node inspector #1483

Merged
merged 4 commits into from
Mar 18, 2024
Merged

feat(horaemeta): add node inspector #1483

merged 4 commits into from
Mar 18, 2024

Conversation

ZuLiangWang
Copy link
Contributor

Rationale

In some extreme scenarios, etcd events may be lost or update failures may occur, which may cause the mapping between nodes and shards to fail to be updated correctly. We need to add a cover-up mechanism to ensure that the mapping relationship is always correct.

Detailed Changes

  • Add NodeInspector, it will start when the cluster start, running in he background and detect the status of nodes.

Test Plan

Pass CI.

Copy link
Contributor

@jiacai2050 jiacai2050 left a comment

Choose a reason for hiding this comment

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

LGTM

@ShiKaiWi ShiKaiWi merged commit 9291dfc into apache:main Mar 18, 2024
4 checks passed
zealchen pushed a commit to zealchen/incubator-horaedb that referenced this pull request Apr 9, 2024
## Rationale
In some extreme scenarios, etcd events may be lost or update failures
may occur, which may cause the mapping between nodes and shards to fail
to be updated correctly. We need to add a cover-up mechanism to ensure
that the mapping relationship is always correct.

## Detailed Changes
* Add `NodeInspector`, it will start when the cluster start, running in
he background and detect the status of nodes.

## Test Plan
Pass CI.

---------

Co-authored-by: xikai.wxk <xikai.wxk@antgroup.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants