similar to: (no subject)

These pairs could be pinged and/or tested before the Filesystem RA tries = to connect to them. In case that one of these nodes is not reachable or = does not respond to the connection attempt the RA could try a connection = with the next nvpair. Background: I would like to build a openais/pacemaker cluster consisting of three = nodes. On each node should run a gluster server providing a

The reason for the long (42 second) ping-timeout is because re-establishing fd's and locks can be a very expensive operation. With an average MTBF of 45000 hours for a server, even just a replica 2 would result in a 42 second MTTR every 2.6 years, or 6 nines of uptime. On December 27, 2017 3:17:01 AM PST, Omar Kohl <omar.kohl at iternity.com> wrote: >Hi, > >> If you set it

Hi, I know that "glusterbot" text about ping-timeout almost by heart by now ;-) I have searched the complete IRC logs and Mailing list from the last 4 or 5 years for anything related to ping-timeout. The problem with "can be a very expensive operation" is that this is extremely vague. It would be helpful to put some numbers behind it. Of course I also understand that any

Pohle at logistik.tu-berlin.de make ; make install Von Samsung Mobile gesendet -------- Urspr?ngliche Nachricht -------- Betreff: [Announce] Samba 3.4.15 Available for Download Von: Karolin Seeger <kseeger at samba.org> An: samba-announce at samba.org,samba at samba.org,samba-technical at samba.org Cc: ================================================================= "Some

Have you checked this page: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html/administration_guide/brick_configuration ? The alignment depends on the HW raid stripe unit size. Best Regards,Strahil Nikolov? On Tue, Jun 6, 2023 at 2:35, mabi<mabi at protonmail.ch> wrote: Hello, I am preparing a brick as LVM thin volume for a test slave node using this

Hello again, for now I figuered out to send a mp3 stream to IceCast with TCP Socket communication. Now I'm challenged with the correct timing for the data packets. Are there any API calls for getting the state of IceCast's buffer? I'm programming now on a scheduler for sending the mp3 frames, depending on the metada of each frame. I hope, that this is precisly enough. Can you tell

Hi, ? Kotresh workaround works for me. But before I tried it, I created some strace-logs for Florian. setup: 2 VMs?(192.168.222.120 master, 192.168.222.121 slave), both with a volume named vol with Ubuntu?16.04.3,?glusterfs 3.13.2, rsync 3.1.1 . ? Best regards, Tino ? root at master:~# cat /usr/bin/rsync #!/bin/bash strace -o /tmp/rsync.trace -ff /usr/bin/rsynco "$@" ? One of the traces

Restarts will go through a shutdown process. As long as the network isn't actively unconfigured before the final kill, the tcp connection will be shutdown and there will be no wait. On 12/28/17 20:19, Sam McLeod wrote: > Sure, if you never restart / autoscale anything and if your use case > isn't bothered with up to 42 seconds of downtime, for us - 42 seconds > is a really

Sure, if you never restart / autoscale anything and if your use case isn't bothered with up to 42 seconds of downtime, for us - 42 seconds is a really long time for something like a patient management system to refuse file attachments from being uploaded etc... We apply a strict patching policy for security and kernel updates, we often also load balance between underlying physical hosts and

Dear Strahil, Thank you very much for pointing me to the RedHat documentation. I wasn't aware of it and it is much more detailed. I will have to read it carefully. Now as I have a single disk (no RAID) based on that documentation I understand that I should use a data alignment value of 256kB. Best regards, Mabi ------- Original Message ------- On Wednesday, June 7th, 2023 at 6:56 AM,

Hi, > If you set it to 10 seconds, and a node goes down, you'll see a 10 seconds freez in all I/O for the volume. Exactly! ONLY 10 seconds instead of the default 42 seconds :-) As I said before the problem with the 42 seconds is that a Windows Samba Client will disconnect (and therefore interrupt any read/write operation) after waiting for about 25 seconds. So 42 seconds is too high. In

advanced in the printer-settings on windows) But if the driver does not get copied over? best regards thomas ________________________________________ Von: "Daniel M=C3=BCller" <mueller at tropenklinik.de> An: "Thomas Stegbauer" <mailingliste1 at stegbauer.info>, "Laurent Blume" = <laurent at opensolaris.org> CC: samba at lists.samba.org Gesendet:

Hello, I am preparing a brick as LVM thin volume for a test slave node using this documentation: https://docs.gluster.org/en/main/Administrator-Guide/formatting-and-mounting-bricks/ but I am confused regarding the right "--dataalignment" option to be used for pvcreate. The documentation mentions the following under point 1: "Create a physical volume(PV) by using the pvcreate

d in the printer-settings on windows)=20 But if the driver does not get copied over?=20 best regards=20 thomas=20 ----- Urspr=C3=BCngliche Mail ----- Von: "Daniel M=C3=BCller" <mueller at tropenklinik.de>=20 An: "Thomas Stegbauer" <mailingliste1 at stegbauer.info>, "Laurent Blume" <lau= rent at opensolaris.org>=20 CC: samba at lists.samba.org=20

Thanks for the reply. We will mainly use this for archival - near-cold storage. Anything, from your experience, to keep in mind while planning large installations? Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Serkan ?oban <cobanserkan at gmail.com> Date: 6/29/17 4:39 AM (GMT-05:00) To: Jason Kiebzak <jkiebzak at gmail.com> Cc: Gluster

>Thanks for the reply. We will mainly use this for archival - near-cold storage. Archival usage is good for EC >Anything, from your experience, to keep in mind while planning large installations? I am using 3.7.11 and only problem is slow rebuild time when a disk fails. It takes 8 days to heal a 8TB disk.(This might be related with my EC configuration 16+4) 3.9+ versions has some

Gluster 4.0! At long last, Gluster 4.0 is released! Read more at: https://www.gluster.org/announcing-gluster-4-0/ Other updates about Gluster 4.0: https://www.gluster.org/more-about-gluster-d2/ https://www.gluster.org/gluster-4-0-kubernetes/ Want to give us feedback about 4.0? We?ve got our retrospective open from now until April 11. https://www.gluster.org/4-0-retrospective/ Welcome piragua!

Gluster Monthly Newsletter, February 2018 Special thanks to all of our contributors working to get Gluster 4.0 out into the wild. Over the coming weeks, we?ll be posting on the blog about some of the new improvements coming out in Gluster 4.0, so watch for that! Glustered: A Gluster Community Gathering is happening on March 8, in connection with Incontro DevOps 2018. More details here:

Announcing mountpoint, August 27-28, 2018 Our inaugural software-defined storage conference combining Gluster, Ceph and other projects! More details at: http://lists.gluster.org/pipermail/gluster-users/2018-May/034039.html CFP at: http://mountpoint.io/ - closes June 15 Gluster Summit Videos - All our available videos (and slides) from Gluster Summit 2017 are up! Check out the

Announcing mountpoint, August 27-28, 2018 Our inaugural software-defined storage conference combining Gluster, Ceph and other projects! More details at: http://lists.gluster.org/pipermail/gluster-users/2018-May/034039.html CFP at: http://mountpoint.io/ Out of cycle updates for all maintained Gluster versions: New updates for 3.10, 3.12 and 4.0