Hi folks,
Can someone give me an idea why gluster and the glusterd
would be taking almost 25% cpu each when under a READ load. (No writing).
I have setup just a simple three node system, and when I put it under a load
of a number of clients; gluster is really killing the cpu.
Gluster Monthly Newsletter, November 2017
Come find us at KubeCon/CloudNativeCon in Austin, December 6-8!
Special sessions around Storage include:
Thursday, December 7 • 11:55am - 12:30pm
Kubernetes Feature Prototyping with External Controllers and Custom
Resource Definitions - Tomas
Hi Jiffin,
I looked at the document, and there are 2 things:
1. In Gluster 3.8 it seems you don't need to do that at all, it creates
this automatically, so why not in 3.10?
2. The step by step guide, in the last item, doesn't say where exactly do I
need to create the nfs-ganesha directory. The
Hi,
Is it possible to create a single node distributed volume ? Later as the
storage capacity starts to fill up, add another node, so on and so forth ?
There are many articles on creating a two node distributed volume, but I
could not find any pointed answer or HOWTOs for creating a single node
On Friday 01 December 2017 03:04 AM, Adam Ru wrote:
Some time ago I read and followed this quide for installing and
configuring Gluster:
http://blog.gluster.org/linux-scale-out-nfsv4-using-nfs-ganesha-and-glusterfs-one-step-at-a-time/
with steps to create certificate:
On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote:
HI,
I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5.
I'm trying to create a very simple 2 nodes cluster to be used with
NFS-ganesha. I've created the bricks and the volume. Here's the output:
# gluster volume info
