search for: markconnor64

Sorry, I meant RedHat's Gluster Storage Server 3.2 which is latest and greatest. On Wed, Aug 2, 2017 at 9:28 AM, Kaushal M <kshlmster at gmail.com> wrote: > On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <markconnor64 at gmail.com> > wrote: > > Can the glusterd daemon be restarted on all storage nodes without causing > > any disruption to data being served or the cluster in general? I am > running > > gluster 3.2 using distributed replica 2 volumes with fuse clients. > > Yes, in...

On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <markconnor64 at gmail.com> wrote: > Can the glusterd daemon be restarted on all storage nodes without causing > any disruption to data being served or the cluster in general? I am running > gluster 3.2 using distributed replica 2 volumes with fuse clients. Yes, in general. Any clients already conne...

Can the glusterd daemon be restarted on all storage nodes without causing any disruption to data being served or the cluster in general? I am running gluster 3.2 using distributed replica 2 volumes with fuse clients. Regards, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have a 10x2 distributed replica volume running gluster3.8. Each of my bricks is about 60TB in size. ( 6TB drives Raid 6 10+2 ) I am running of storage so I intend on adding servers with larger 8Tb drives. My new bricks will be 80TB in size. I will make sure the replica to the larger brick will match in size. Will gluster place more files on the larger bricks? Or will I have wasted space? In

Folks, I need to update all my gluserfs-fuse clients to the latest version. Can I do this without a reboot? If I stop the module then update the fuse client, would this suffice? Or do I really need a reboot? Thank You -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171114/438530ee/attachment.html>

All my 3.8 fuse clients have big dumpfiles that eventually fill up /var. -bash-4.1$ ls -lh /var/run/gl* total 1.5G -rw------- 1 root root 308K Dec 8 03:34 glusterdump.31050.dump.1512722042 -rw------- 1 root root 315K Dec 8 03:34 glusterdump.31124.dump.1512722042 -rw------- 1 root root 1.5G Dec 8 03:36 glusterdump.9314.dump.1512722042 I believe this may be part of the rotatelog config.

Folks, need help interpreting this message from my geo rep logs for my volume mojo. ssh%3A%2F%2Froot%40173.173.241.2%3Agluster%3A%2F%2F127.0. 0.1%3Amojo-remote.log:[2017-11-22 00:59:40.610574] I [master(/bricks/lsi/mojo):1125:crawl] _GMaster: slave's time: (1511312352, 0) The epoch of 1511312352 is Tuesday, November 21, 2017 12:59:12 AM GMT. The clocks are using the same ntp stratum and

Has anyone applied patches to gluster storage node or fuse clients in an attempt to address Meltdown/Spectre issues? I'm curious if anyone has noticed or expects to see a performance impact. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180117/28573776/attachment.html>

I am running gluster ver 3.8 in a distributed replica 2 config. I need to reboot all my 8 cluster nodes to update my bios firmware. I would like to do a rolling update to my bios and keep up my cluster so my clients don't take an outage. Do I need to shutdown all gluster services on each node before I reboot? Or just issue the reboot. -------------- next part -------------- An HTML attachment