<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Khoi,<div><br></div><div>I found a large changelog in the source package <a href="http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.3.2.tar.gz">http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.3.2.tar.gz</a> <br><div><div><br></div><div>For production, depends on what you are going to do.</div><div>If you work a lot with virtual machine, then 3.4.0 will <span id="result_box" class="short_text" lang="en">probably what you want.</span></div><div><br></div><div>We are stay with 3.3.2 (upgrdae to night) until 3.4.1 is releases.</div><div><br></div><div>Grtz, Jiri</div><div><br></div><div>On Jul 22, 2013, at 4:43 PM, "Khoi Mai" <<a href="mailto:KHOIMAI@UP.COM">KHOIMAI@UP.COM</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><font size="2" face="sans-serif">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?</font><br><br><font size="2" face="sans-serif">Thanks,</font><br><font size="2" face="sans-serif"><br><br>Khoi<br><br></font><br><br><br><br><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif"><a href="mailto:gluster-users-request@gluster.org">gluster-users-request@gluster.org</a></font><br><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif"><a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a></font><br><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">07/19/2013 06:59 AM</font><br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Gluster-users
Digest, Vol 63, Issue 62</font><br><font size="1" color="#5f5f5f" face="sans-serif">Sent by:
</font><font size="1" face="sans-serif"><a href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a></font><br><hr noshade=""><br><br><br><tt><font size="2">Send Gluster-users mailing list submissions to<br>
<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>
</font></tt><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"><tt><font size="2">http://supercolony.gluster.org/mailman/listinfo/gluster-users</font></tt></a><tt><font size="2"><br>or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gluster-users-request@gluster.org">gluster-users-request@gluster.org</a><br><br>You can reach the person managing the list at<br>
<a href="mailto:gluster-users-owner@gluster.org">gluster-users-owner@gluster.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Gluster-users digest..."<br><br><br>Today's Topics:<br><br> 1. Re: One node goes offline, the other node can't see the<br> replicated volume anymore (Greg Scott)<br> 2. Re: GlusterFS 3.4.0 and 3.3.2 released! (Jacob Yundt)<br> 3. How do I rotate **all** the Gluster logs? (Greg Scott)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 18 Jul 2013 21:20:28 +0000<br>From: Greg Scott <<a href="mailto:GregScott@infrasupport.com">GregScott@infrasupport.com</a>><br>To: 'Ben Turner' <<a href="mailto:bturner@redhat.com">bturner@redhat.com</a>><br>Cc: "<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>" <<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>><br>Subject: Re: [Gluster-users] One node goes offline, the other node<br>
can't see the replicated volume anymore<br>Message-ID:<br>
<9de1ce076e1d4a4f9d3cc5193a12041e@mail2013.infrasupport.local><br>Content-Type: text/plain; charset="utf-8"<br><br>> You can set the timeout with:<br>><br>> $ gluster volume set <volname> network.ping-timeout <N><br>><br>> I don't usually set it to anything under 20.<br>><br><br>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?<br><br>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. <br><br>Thanks<br><br>- Greg<br><br><br>-----Original Message-----<br>From: Ben Turner [</font></tt><a href="mailto:bturner@redhat.com"><tt><font size="2">mailto:bturner@redhat.com</font></tt></a><tt><font size="2">]
<br>Sent: Thursday, July 18, 2013 9:33 AM<br>To: Greg Scott<br>Cc: Joe Julian; <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>Subject: Re: [Gluster-users] One node goes offline, the other node can't
see the replicated volume anymore<br><br>You can set the timeout with:<br><br>$ gluster volume set <volname> network.ping-timeout <N><br><br>I don't usually set it to anything under 20. <br><br>-b<br><br>----- Original Message -----<br>> From: "Greg Scott" <<a href="mailto:GregScott@infrasupport.com">GregScott@infrasupport.com</a>><br>> To: "Joe Julian" <<a href="mailto:joe@julianfamily.org">joe@julianfamily.org</a>><br>> Cc: "<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>" <<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>><br>> Sent: Thursday, July 18, 2013 1:00:50 AM<br>> Subject: Re: [Gluster-users] One node goes offline, the other node
<br>> can't see the replicated volume anymore<br>> <br>> <br>> <br>> Still not out of the woods. I can get everything mounted on both nodes
<br>> with my systemd service hack. But now I?m back to the original <br>> problem. Well, sort of. Here is the scenario.<br>> <br>> <br>> <br>> My Gluster volume named /firewall-scripts is mounted on both fw1 and
fw2.<br>> Trying to simulate a cable issue, on fw1, I do:<br>> <br>> <br>> <br>> ifdown enp5s4<br>> <br>> <br>> <br>> And now all access to my /firewall-scripts volume on fw1 goes away.
<br>> Fw2 can see it after more than the mystical 42 seconds. When I do<br>> <br>> <br>> <br>> ifup enp4s4<br>> <br>> <br>> <br>> I still can?t see my /firewall-scripts volume on fw1 and it is no
<br>> longer mounted. Not quite one minute later, my volume is mounted again
<br>> and life goes on.<br>> <br>> <br>> <br>> If that 42 second timeout is settable, how do I set it for a better
<br>> number for my application? The Gluster/Heartbeat network in this case
<br>> will just be a cable connecting the two nodes.<br>> <br>> <br>> <br>> Thanks<br>> <br>> <br>> <br>> - Greg<br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> Gluster-users mailing list<br>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>> </font></tt><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"><tt><font size="2">http://supercolony.gluster.org/mailman/listinfo/gluster-users</font></tt></a><tt><font size="2"><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 18 Jul 2013 17:28:38 -0400<br>From: Jacob Yundt <<a href="mailto:jyundt@gmail.com">jyundt@gmail.com</a>><br>To: Vijay Bellur <<a href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>><br>Cc: gluster-users Discussion List <<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>><br>Subject: Re: [Gluster-users] GlusterFS 3.4.0 and 3.3.2 released!<br>Message-ID:<br>
<<a href="mailto:CAG0kxBd38oph7=pdKUN2DS1mEoCAkqesEOR=Mua6RLhduWhoWQ@mail.gmail.com">CAG0kxBd38oph7=pdKUN2DS1mEoCAkqesEOR=Mua6RLhduWhoWQ@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>>> 2. In release Notes for 3.4.0 it is stated that ext4-issue has
been<br>>> addressed - does this mean that it is safe to use ext4 with later<br>>> kernels now?<br>>><br>><br>> There are no known problems with ext4 and 3.4.0, even with newer kernels.<br>><br><br>Just to be perfectly clear, does this mean that the DHT[1] problem<br>with RHEL6 kernels > 2.6.32-267 has been resolved in gluster 3.4.0?<br>If so, I'm probably going to start switching bricks to ext4 until I<br>can get my xfs problem[2] resolved.<br><br>-Jacob<br><br>[1] </font></tt><a href="https://bugzilla.redhat.com/show_bug.cgi?id=838784"><tt><font size="2">https://bugzilla.redhat.com/show_bug.cgi?id=838784</font></tt></a><tt><font size="2"><br>[2] </font></tt><a href="https://bugzilla.redhat.com/show_bug.cgi?id=958781"><tt><font size="2">https://bugzilla.redhat.com/show_bug.cgi?id=958781</font></tt></a><tt><font size="2"><br><br><br>------------------------------<br><br>Message: 3<br>Date: Fri, 19 Jul 2013 11:08:38 +0000<br>From: Greg Scott <<a href="mailto:GregScott@infrasupport.com">GregScott@infrasupport.com</a>><br>To: "'<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>'" <<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>><br>Subject: [Gluster-users] How do I rotate **all** the Gluster logs?<br>Message-ID:<br>
<33b641bb8e344afa919d35dc8a74ee3e@mail2013.infrasupport.local><br>Content-Type: text/plain; charset="us-ascii"<br><br>I know I can do:<br><br>gluster log rotate <volume name><br><br>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.<br><br>What am I missing?<br><br>Thanks<br><br><br>- Greg Scott<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</font></tt><a href="http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130719/fa431b4c/attachment-0001.html"><tt><font size="2">http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130719/fa431b4c/attachment-0001.html</font></tt></a><tt><font size="2">><br><br>------------------------------<br><br>_______________________________________________<br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br></font></tt><a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"><tt><font size="2">http://supercolony.gluster.org/mailman/listinfo/gluster-users</font></tt></a><tt><font size="2"><br><br>End of Gluster-users Digest, Vol 63, Issue 62<br>*********************************************<br></font></tt><br><br>
**<br>
<br>
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.<br>
**<br>_______________________________________________<br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>http://supercolony.gluster.org/mailman/listinfo/gluster-users</blockquote></div><br></div></body></html>