[Gluster-users] Performance issues with one node

John Kennedy skebi69 at gmail.com
Fri Jul 24 17:34:46 UTC 2015


I am new to Gluster and have not found anything useful from my friend
Google. I have not dealt with physical hardware in a few years (my last few
jobs have been VM's and AWS based)

I inherited a 4 node gluster configuration. There are 2 bricks, one is 9TB
the other 11TB.

The 11TB brick has a HUGE number of small files taking up only 1.3TB of the
brick. For some reason, even a simple ls command can take hours to even
start listing files. I removed a node by shutting down gluster on that
node. The change in performance is dramatic. If I try and do ls on the 11TB
brick on the downed node, I am still getting the slow response. I have
narrowed the issue down to this one node as a result.

When I start gluster on the bad node, glusterfsd hits over 1000%CPU use
(The server has dual 8 core CPU's) and the load will jump to 25-30 within 5
minutes. As such, I think this is a gluster issue and not a hardware issue.
I am trying to not reinstall gluster yet.

Is there something I am missing in my checks or will I need to reinstall
gluster on that node?

Thanks,
John

John Kennedy  (_8(|)
Sometimes it happens, sometimes it doesn't - Pedro Catacora

Just because nobody disagrees with you doesn't mean you are correct.

Anatidaephobia is the fear that somehow, somewhere a duck is watching you -
urbandictionary.com

The Dunning-Kruger effect occurs when incompetent people not only fail to
realize their incompetence, but consider themselves much more competent
than everyone else. Basically - they're too stupid to know that they're
stupid.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150724/e67af6c8/attachment.html>


More information about the Gluster-users mailing list