I second Paul's remarks, and am much heartened by this report. I have noticed that the Gluster dev and support folks have definitely increased their responsiveness and depth of their answers. Much appreciated - keep up the good work! James Burnash Unix Engineer Knight Capital Group From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of paul simpson Sent: Thursday, June 16, 2011 6:29 AM To: vs at gluster.com Cc: gluster-users at gluster.org Subject: Re: Fwd: Re: Inputs requested on 3.2.0 hi vidya, thanks very much for this very comprehensive summary. it's most reassuring to read - this is exactly what the community needs. looking forward to further reports and releases... regards, paul On 15 June 2011 14:57, Vidya Sakar <vs at gluster.com<mailto:vs at gluster.com>> wrote: Hi all, A couple of weeks back I had sought inputs from you all on 3.2.0 and I had committed to revert back with an action plan to address all concerns/suggestions. As you would have noticed, 3.2.1 was released a few days ago - already addressing some of your concerns. Please keep the feedback coming, inputs from the community are very important to us. Please find below responses to each of your concerns / suggestions : 1) Stability : (Paul simpson, James Burnash, Mohit Anchlia) This is of utmost importance to us. We are investing more in QA engineers, QA lead and also in engineers who will dedicatedly work only on bug fixes. We are refining our development processes focusing more on quality and stability. We are increasing the test coverage and automating the tests along with more investments in lab infrastructure. 2) Better way to handle errors and failures, better troubleshooting tools : (James Burnash, Whit Blauvelt) The scale of the number of components and systems involved increases the need for better troubleshooting tools and better handling of errors and failures. The recently introduced top/profile is a step in this direction to build diagnosability in to the product. There was also an effort on improving log messages in all modules - to make them more meaningful, prioritizing them appropriately, introducing new logs where necessary and things like that. The recently completed enhancements around logging in 3.2.0 is only the first of a multi-phase effort to improve logging and make the user experience much better. 3) Better documentation : (Udo Waechter, Christian Kauhaus) We are revamping the documentation and we should soon have more content in existing sections and we will also have new content - things like troubleshooting section, performance tuning section, best practices section are all in the pipeline. The format of documentation is also due for a change shortly. 4) Posix compatibility : (Paul simpson, Udo Waechter) We are fully committed to POSIX compatibility. Scenarios where it is not compatible if any would be high priority bugs for us. 5) Better self-heal / reporting on which files are not replicated : (Paul simpson, Whit Blauvelt) This is already in our roadmap for 3.3. It is actively being worked on and we can soon expect improvements in this area. 6) NFS nlm locking : (Paul simpson) We do realize the need for NLM, I will get back to you all shortly on what our plan on NLM is going to be. 7) Ability to list config settings (including default) / Performance settings and benchmarks : (Mike Hanby, Udo Waechter) The list of defaults is given in this blog post : http://sacurs.blogspot.com/2011/05/glusterfs-defaults.html And we also have a bug for this : http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041 8) Bugs : (Mohit Anchlia, Udo Waechter) 1) gfid mismatch issue : Is this bug 2522? Please let me know if you are referring to something else 2) 0 byte file size : Bug 2922, we are working on it 3) Multiple files of same name showing up on the clent side : This problem too will get addressed as part of fixing 2522. 4) client hangs and crash : There are some related bugs which we fixed in 3.2.1, if this issue still persists, we are committed to fix the remaining issues. 5) xattr mismatch on gluster mount points causing split brain errors : This issue too is fixed in 3.2.1. 6) non-root owned files not shown : Bug 3030 has been filed to track this. Thanks, VS -- Vidya Sakar N Senior Engineering Manager Gluster Software India (P) Ltd Bangalore -------- Original Message -------- Subject: Re: Inputs requested on 3.2.0 Date: Thu, 26 May 2011 20:38:30 +0530 From: Vidya Sakar <vs at gluster.com><mailto:vs at gluster.com> To: gluster-users at gluster.org<mailto:gluster-users at gluster.org> Thanks to everyone for all the inputs. I will get back with responses to each of your suggestions shortly. Thanks, VS -- Vidya Sakar N Senior Engineering Manager Gluster Software India (P) Ltd Bangalore On Wednesday 25 May 2011 10:54 PM, Mohit Anchlia wrote: > Hi Vidya, > > Thanks for asking. I think it will be worthwhile to look at the > archives and mailing list to see what other people have reported for > 3.2. Few people already downgraded so not sure if they filed a bug. > But things that I have heard here: > > 1) gfid mismatch issue. Bug was filed > 2) 0 byte file size. Bug was filed > 3) Multiple files of same name showing up on the clent side > 4) client hangs and crash > 5) xattr mismatch on gluster mount points causing split brain errors. > Bug was filed > > I certainly want to use 3.2 for geo-rep feature but problems that I am > seeing that others have faced has put me back and waiting for 3.2 to > become more stable. It will be really good to make 3.2 really solid > and stable. > > Thanks > > On Wed, May 25, 2011 at 8:25 AM, Udo Waechter > <udo.waechter at uni-osnabrueck.de><mailto:udo.waechter at uni-osnabrueck.de> wrote: > >> Hi, >> for us, gluster 3.2.0 really messed up everything in a distribute/replicate setup. Everything should be mentioned in this thread. http://gluster.org/pipermail/gluster-users/2011-May/007705.html >> >> The most important features for us would be: >> 1. 100% posix compatibility (this is already mentioned as a feature in the FAQ!!!) >> 2. Better documentation. All the options and their settings do not really explain what they do. >> I could guess that performance.cache-size somehow influences performance, but for us changing it to very high (4Gbs and more) and very low (128Mb) did not change a thing. Same for stat-prefetch (which is supposed to makels quickier) on/off: nothing. Would be nice to see some scenarios/settingsand their benchmarks. >> >> Thanks for the effort, >> udo. >> >> On 24.05.2011, at 12:52, Vidya Sakar wrote: >> >> >>> Hello all, >>> >>> We are planing a 3.2.1 release and we would like to hear from you all on the specific concerns you may have about 3.2.0 stability and any bugs that you are hitting in 3.2.0 (if they already have not been filed yet). Inputs on 3.1.x is welcome too, please be specific on the information you provide us. Community feedback is of paramount importance to us, please file bugsto help us address them soon. >>> >>> Thanks, >>> VS >>> >>> -- >>> Vidya Sakar N >>> Senior Engineering Manager >>> Gluster Software India (P) Ltd >>> Bangalore >>> >>> _______________________________________________ >>> Gluster-users mailing list >>> Gluster-users at gluster.org<mailto:Gluster-users at gluster.org> >>> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >>> >>> >> -- >> :: udo waechter - root at zoide.net<mailto:root at zoide.net> :: N 52?16'30.5" E 8?3'10.1" >> :: genuine input for your ears: http://auriculabovinari.de >> :: your eyes: http://ezag.zoide.net >> :: your brain: http://zoide.net >> >> >> >> >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org<mailto:Gluster-users at gluster.org> >> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >> >> >> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org<mailto:Gluster-users at gluster.org> > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org<mailto:Gluster-users at gluster.org> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org<mailto:Gluster-users at gluster.org> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users DISCLAIMER: This e-mail, and any attachments thereto, is intended only for use by the addressee(s)named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com<http://www.knight.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20110616/4fabf3ba/attachment-0001.htm>
