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

[DocDB] Dump PeerManager to tserver debug ui consensus page #18465

Closed
1 task done
Huqicheng opened this issue Jul 28, 2023 · 0 comments
Closed
1 task done

[DocDB] Dump PeerManager to tserver debug ui consensus page #18465

Huqicheng opened this issue Jul 28, 2023 · 0 comments
Assignees
Labels
2.14 Backport Required 2.16 Backport Required 2.18 Backport Required area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@Huqicheng
Copy link
Contributor

Huqicheng commented Jul 28, 2023

Jira Link: DB-7438

Description

To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@Huqicheng Huqicheng added the area/docdb YugabyteDB core features label Jul 28, 2023
@Huqicheng Huqicheng self-assigned this Jul 28, 2023
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue labels Jul 28, 2023
Huqicheng added a commit that referenced this issue Aug 4, 2023
Summary:
To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

When dumping the peer manager, need to acquire the peer manager lock and the peer lock, if the peer is in a bad state (deadlock, etc), might get http request timed out.
Jira: DB-7438

Test Plan: Manual test: Start rf-3 unverse, create a tablet. curl `LEADER_IP:9000/tablet-consensus-status?id=TABLET_ID` to check the result.

Reviewers: kpopali

Reviewed By: kpopali

Subscribers: bogdan, ybase

Differential Revision: https://phorge.dev.yugabyte.com/D27459
Huqicheng added a commit that referenced this issue Aug 8, 2023
…onsensus page

Summary:
Original commit: 288c989 / D27459
To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

When dumping the peer manager, need to acquire the peer manager lock and the peer lock, if the peer is in a bad state (deadlock, etc), might get http request timed out.
Jira: DB-7438

Test Plan: Manual test: Start rf-3 unverse, create a tablet. curl `LEADER_IP:9000/tablet-consensus-status?id=TABLET_ID` to check the result.

Reviewers: kpopali

Reviewed By: kpopali

Subscribers: ybase, bogdan

Differential Revision: https://phorge.dev.yugabyte.com/D27568
Huqicheng added a commit that referenced this issue Aug 8, 2023
…onsensus page

Summary:
Original commit: 288c989 / D27459
To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

When dumping the peer manager, need to acquire the peer manager lock and the peer lock, if the peer is in a bad state (deadlock, etc), might get http request timed out.
Jira: DB-7438

Test Plan: Manual test: Start rf-3 unverse, create a tablet. curl `LEADER_IP:9000/tablet-consensus-status?id=TABLET_ID` to check the result.

Reviewers: kpopali

Reviewed By: kpopali

Subscribers: ybase, bogdan

Differential Revision: https://phorge.dev.yugabyte.com/D27569
Huqicheng added a commit that referenced this issue Aug 10, 2023
…onsensus page

Summary:
Original commit: 288c989 / D27459
To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

When dumping the peer manager, need to acquire the peer manager lock and the peer lock, if the peer is in a bad state (deadlock, etc), might get http request timed out.
Jira: DB-7438

Test Plan: Manual test: Start rf-3 unverse, create a tablet. curl `LEADER_IP:9000/tablet-consensus-status?id=TABLET_ID` to check the result.

Reviewers: kpopali

Reviewed By: kpopali

Subscribers: ybase, bogdan

Differential Revision: https://phorge.dev.yugabyte.com/D27567
karan-yb pushed a commit that referenced this issue Aug 24, 2023
… consensus page

Summary:
Original commit: 12a44ba / D27568
To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

When dumping the peer manager, need to acquire the peer manager lock and the peer lock, if the peer is in a bad state (deadlock, etc), might get http request timed out.
Jira: DB-7438

Test Plan: Manual test: Start rf-3 unverse, create a tablet. curl `LEADER_IP:9000/tablet-consensus-status?id=TABLET_ID` to check the result.

Reviewers: qhu, bogdan

Reviewed By: qhu, bogdan

Subscribers: bogdan, ybase

Differential Revision: https://phorge.dev.yugabyte.com/D28077
karan-yb pushed a commit that referenced this issue Sep 28, 2023
…i consensus page

Summary:
Original commit: 288c989 / D27459
To debug a case where a follower is possibly not tracked at leader side, we can dump PeerManager to the consensus state page and get a clear view of it.

When dumping the peer manager, need to acquire the peer manager lock and the peer lock, if the peer is in a bad state (deadlock, etc), might get http request timed out.
Jira: DB-7438

Test Plan:
Manual test: Start rf-3 unverse, create a tablet. curl `LEADER_IP:9000/tablet-consensus-status?id=TABLET_ID` to check the result.
Jenkins: urgent
Jenkins: compile only

Reviewers: qhu, bogdan

Reviewed By: bogdan

Subscribers: ybase, bogdan

Differential Revision: https://phorge.dev.yugabyte.com/D28909
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.14 Backport Required 2.16 Backport Required 2.18 Backport Required area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

3 participants