Its not uncommon for gluster to spike up to use more than a whole core.
You may simply be exhausting the effective write cache on the gluster servers in which case unless you are striping your data across many raids you may just be hitting the limits of your hardware.
You may also have client(s) that are asymetricly connecting to only one or a small subset of servers due to a connectivity issue which would cause that one node or group of nodes to bear the brunt of replicating the entire workload via constant self heal.
To help you I would rather know more about your configuration before giving advice.
-- Sent from my HP Pre3
On Jan 28, 2014 14:08, Harshavardhana <harsha@xxxxxxxxxxxxxxxxxx> wrote:
You should take a 'gluster' statedump of the process - and open a
bugzilla for analysis with logs.
On Tue, Jan 28, 2014 at 10:30 AM, Jay Vyas <jayunit100@xxxxxxxxx> wrote:
> Hi folks :
>
> Im running mahout on top of gluster using the GlusterFileSystem hadoop
> plugin.
>
> It works well, but Im noticing that glusterfsd is at 100% CPU, and a copy
> action seems to be stalling after a long workload.
>
> Any ways to rescue the system? or should i restart it ?
>
> --
> Jay Vyas
> http://jayunit100.blogspot.com
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
--
Religious confuse piety with mere ritual, the virtuous confuse
regulation with outcomes
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
