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

[bug:1806244] An issue where the cpu iowait and load of the glusterfs-server alternately rise. #878

Closed
gluster-ant opened this issue Mar 12, 2020 · 2 comments
Labels
Migrated Type:Bug wontfix Managed by stale[bot]

Comments

@gluster-ant
Copy link
Collaborator

URL: https://bugzilla.redhat.com/1806244
Creator: knjeong at growthsoft.co.kr
Time: 20200223T08:29:42

Created attachment 1665166
glusterfs-server cpu load graph

Description of problem:

Our glusterfs-volume(3.12.15) consists of 3 replications as shown below.

Volume Name: nas
Type: Distributed-Replicate
Volume ID: 5a8cc386-85dc-4255-b287-352a499a28d5
Status: Started
Snapshot Count: 0
Number of Bricks: 2 x 3 = 6
Transport-type: tcp
Bricks:
Brick1: NAS01:/gluster1/nas
Brick2: NAS02:/gluster1/nas
Brick3: NAS03:/gluster1/nas
Brick4: NAS01:/gluster2/nas
Brick5: NAS02:/gluster2/nas
Brick6: NAS03:/gluster2/nas

The current issue is the alternating cpu iowait and cpu load on three glusterfs-servers, with one, two or three simultaneously rising.

It was confirmed that iowait rises first before the load goes up.

However, since it is a volume consisting of 3 replications, the amount of reads and writes is similar, making it difficult to analyze the cause.

The issue started from the day I remounted the volume on two clients (February 5), and I tried to remount and reboot the glusterfs-server to solve the problem, but to no avail.

Can someone give me an answer?

Version-Release number of selected component (if applicable): 3.12.15

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

@stale
Copy link

stale bot commented Oct 8, 2020

Thank you for your contributions.
Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity.
It will be closed in 2 weeks if no one responds with a comment here.

@stale stale bot added the wontfix Managed by stale[bot] label Oct 8, 2020
@stale
Copy link

stale bot commented Oct 23, 2020

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.

@stale stale bot closed this as completed Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Migrated Type:Bug wontfix Managed by stale[bot]
Projects
None yet
Development

No branches or pull requests

1 participant