[Gluster-users] GlusterFS 3.4.0 and 3.3.2 released!

Mon Jul 22 14:54:41 UTC 2013

Hi Khoi,

I found a large changelog in the source package http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.3.2.tar.gz 

For production, depends on what you are going to do.
If you work a lot with virtual machine, then 3.4.0 will probably what you want.

We are stay with 3.3.2 (upgrdae to night) until 3.4.1 is releases.

Grtz, Jiri

On Jul 22, 2013, at 4:43 PM, "Khoi Mai" <KHOIMAI at UP.COM> wrote:

> Where may I find release docs. on what is new on 3.3.2, and which release should I lean towards if I want to head into production?
> 
> Thanks,
> 
> 
> Khoi
> 
> 
> 
> 
> 
> From:        gluster-users-request at gluster.org
> To:        gluster-users at gluster.org
> Date:        07/19/2013 06:59 AM
> Subject:        Gluster-users Digest, Vol 63, Issue 62
> Sent by:        gluster-users-bounces at gluster.org
> 
> 
> 
> Send Gluster-users mailing list submissions to
>                 gluster-users at gluster.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>                 http://supercolony.gluster.org/mailman/listinfo/gluster-users
> or, via email, send a message with subject or body 'help' to
>                 gluster-users-request at gluster.org
> 
> You can reach the person managing the list at
>                 gluster-users-owner at gluster.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gluster-users digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: One node goes offline, the other node can't see the
>      replicated volume anymore (Greg Scott)
>   2. Re: GlusterFS 3.4.0 and 3.3.2 released! (Jacob Yundt)
>   3. How do I rotate **all** the Gluster logs? (Greg Scott)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 18 Jul 2013 21:20:28 +0000
> From: Greg Scott <GregScott at infrasupport.com>
> To: 'Ben Turner' <bturner at redhat.com>
> Cc: "gluster-users at gluster.org" <gluster-users at gluster.org>
> Subject: Re: [Gluster-users] One node goes offline, the other node
>                 can't see the replicated volume anymore
> Message-ID:
>                 <9de1ce076e1d4a4f9d3cc5193a12041e at mail2013.infrasupport.local>
> Content-Type: text/plain; charset="utf-8"
> 
> > You can set the timeout with:
> >
> > $ gluster volume set <volname> network.ping-timeout <N>
> >
> > I don't usually set it to anything under 20.
> >
> 
> I was just getting ready to put this in, but a bunch more questions are filling my head.  The biggie is, how do I look up the current setting?  Gluster volume info doesn't show me that number.  Is there something else that can show all the detailed settings?
> 
> I was thinking of setting it down to as little as 5 seconds.  And even 5 seconds might be too long.  In my specific use case, my failover script polls the active partner every 10 seconds.  By default, if he doesn't respond in 2 intervals (20 seconds), I initiate my failover stuff.  When I start a failover, I really really really need that /firewall-scripts directory to be usable.   this specific use case, I'm not sure it makes sense to wait 20 seconds.  But before I mess with it, I want to see where it's set right now so I have a baseline.  
> 
> Thanks
> 
> - Greg
> 
> 
> -----Original Message-----
> From: Ben Turner [mailto:bturner at redhat.com] 
> Sent: Thursday, July 18, 2013 9:33 AM
> To: Greg Scott
> Cc: Joe Julian; gluster-users at gluster.org
> Subject: Re: [Gluster-users] One node goes offline, the other node can't see the replicated volume anymore
> 
> You can set the timeout with:
> 
> $ gluster volume set <volname> network.ping-timeout <N>
> 
> I don't usually set it to anything under 20. 
> 
> -b
> 
> ----- Original Message -----
> > From: "Greg Scott" <GregScott at infrasupport.com>
> > To: "Joe Julian" <joe at julianfamily.org>
> > Cc: "gluster-users at gluster.org" <gluster-users at gluster.org>
> > Sent: Thursday, July 18, 2013 1:00:50 AM
> > Subject: Re: [Gluster-users] One node goes offline, the other node 
> > can't see the replicated volume anymore
> > 
> > 
> > 
> > Still not out of the woods. I can get everything mounted on both nodes 
> > with my systemd service hack. But now I?m back to the original 
> > problem. Well, sort of. Here is the scenario.
> > 
> > 
> > 
> > My Gluster volume named /firewall-scripts is mounted on both fw1 and fw2.
> > Trying to simulate a cable issue, on fw1, I do:
> > 
> > 
> > 
> > ifdown enp5s4
> > 
> > 
> > 
> > And now all access to my /firewall-scripts volume on fw1 goes away. 
> > Fw2 can see it after more than the mystical 42 seconds. When I do
> > 
> > 
> > 
> > ifup enp4s4
> > 
> > 
> > 
> > I still can?t see my /firewall-scripts volume on fw1 and it is no 
> > longer mounted. Not quite one minute later, my volume is mounted again 
> > and life goes on.
> > 
> > 
> > 
> > If that 42 second timeout is settable, how do I set it for a better 
> > number for my application? The Gluster/Heartbeat network in this case 
> > will just be a cable connecting the two nodes.
> > 
> > 
> > 
> > Thanks
> > 
> > 
> > 
> > - Greg
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://supercolony.gluster.org/mailman/listinfo/gluster-users
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 18 Jul 2013 17:28:38 -0400
> From: Jacob Yundt <jyundt at gmail.com>
> To: Vijay Bellur <vbellur at redhat.com>
> Cc: gluster-users Discussion List <Gluster-users at gluster.org>
> Subject: Re: [Gluster-users] GlusterFS 3.4.0 and 3.3.2 released!
> Message-ID:
>                 <CAG0kxBd38oph7=pdKUN2DS1mEoCAkqesEOR=Mua6RLhduWhoWQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> >> 2. In release Notes for 3.4.0 it is stated that ext4-issue has been
> >> addressed - does this mean that it is safe to use ext4 with later
> >> kernels now?
> >>
> >
> > There are no known problems with ext4 and 3.4.0, even with newer kernels.
> >
> 
> Just to be perfectly clear, does this mean that the DHT[1] problem
> with RHEL6 kernels > 2.6.32-267 has been resolved in gluster 3.4.0?
> If so, I'm probably going to start switching bricks to ext4 until I
> can get my xfs problem[2] resolved.
> 
> -Jacob
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=838784
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=958781
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 19 Jul 2013 11:08:38 +0000
> From: Greg Scott <GregScott at infrasupport.com>
> To: "'gluster-users at gluster.org'" <gluster-users at gluster.org>
> Subject: [Gluster-users] How do I rotate **all** the Gluster logs?
> Message-ID:
>                 <33b641bb8e344afa919d35dc8a74ee3e at mail2013.infrasupport.local>
> Content-Type: text/plain; charset="us-ascii"
> 
> I know I can do:
> 
> gluster log rotate <volume name>
> 
> and I see how that rotates log files in /var/log/glusterfs/bricks.  This is good.  But there's another log file, /var/log/glusterfs/<volume name>.log and that one doesn't seem to rotate.    There are also a bunch of others in that directory and I don't see any evidence the above command makes them rotate.
> 
> What am I missing?
> 
> Thanks
> 
> 
> -          Greg Scott
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130719/fa431b4c/attachment-0001.html>
> 
> ------------------------------
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
> 
> End of Gluster-users Digest, Vol 63, Issue 62
> *********************************************
> 
> 
> **
> 
> This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient. Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law. If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
> **
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130722/31c9c93a/attachment.html>