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

PRIMARY timeouted after secondary node rebooted and joined cluster(minutes after) - RDMA #89

Open
Lathanderjk opened this issue May 7, 2024 · 0 comments
Open

PRIMARY timeouted after secondary node rebooted and joined cluster(minutes after) - RDMA #89

Lathanderjk opened this issue May 7, 2024 · 0 comments

Comments

@Lathanderjk
Copy link

Lathanderjk commented May 7, 2024 •
edited
Loading

We are updating to 9.2.9, one of nodes was updated few days back, today after updating second one and rebooting, PRIMARY(which was still 9.2.8) timeouted for more than 60s(FS monitor timeout), it happened after secondary which was rebooted was joined...

PRIMARY system load during timeout decreased and IO busy/throughput on underlaing drives goes down to zero.

I marked time when timeout start in log.
log.txt
filesystem.res.txt
@Lathanderjk Lathanderjk changed the title PRIMARY timeouted after secondary node rebooted and joined cluster(minutes after) PRIMARY timeouted after secondary node rebooted and joined cluster(minutes after) - RDMA May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lathanderjk