similar to: new Gluster cluster: 3.10 vs 3.12

http://lists.gluster.org/pipermail/gluster-users/2018-February/033532.html On Fri, Feb 23, 2018 at 10:38 AM, Anatoliy Dmytriyev <tolid at tolid.eu.org> wrote: > Hi > > We are planning to install new gluster cluster and I am wondering which > gluster LTM version will you suggest to install: 3.10 or 3.12 in terms of > stability, performance and bugs free version. It will be

On Wed, Mar 14, 2018 at 3:36 PM, Anatoliy Dmytriyev <tolid at tolid.eu.org> wrote: > Hi Karthik, > > > Thanks a lot for the explanation. > > Does it mean a distributed volume health can be checked only by "gluster > volume status " command? > Yes. I am not aware of any other command which can give the status of plain distribute volume which is similar to

Hi Anatoliy, The heal command is basically used to heal any mismatching contents between replica copies of the files. For the command "gluster volume heal <volname>" to succeed, you should have the self-heal-daemon running, which is true only if your volume is of type replicate/disperse. In your case you have a plain distribute volume where you do not store the replica of any

On Wed, Mar 14, 2018 at 5:42 PM, Karthik Subrahmanya <ksubrahm at redhat.com> wrote: > > > On Wed, Mar 14, 2018 at 3:36 PM, Anatoliy Dmytriyev <tolid at tolid.eu.org> > wrote: > >> Hi Karthik, >> >> >> Thanks a lot for the explanation. >> >> Does it mean a distributed volume health can be checked only by "gluster >> volume

Hi Karthik, Thanks a lot for the explanation. Does it mean a distributed volume health can be checked only by "gluster volume status " command? And one more question: cluster.min-free-disk is 10% by default. What kind of "side effects" can we face if this option will be reduced to, for example, 5%? Could you point to any best practice document(s)? Regards, Anatoliy

Can we add a smarter error message for this situation by checking volume type first? Cheers, Laura B On Wednesday, March 14, 2018, Karthik Subrahmanya <ksubrahm at redhat.com> wrote: > Hi Anatoliy, > > The heal command is basically used to heal any mismatching contents > between replica copies of the files. > For the command "gluster volume heal <volname>"

Hi, Maybe someone can point me to a documentation or explain this? I can't find it myself. Do we have any other useful resources except doc.gluster.org? As I see many gluster options are not described there or there are no explanation what is doing... On 2018-03-12 15:58, Anatoliy Dmytriyev wrote: > Hello, > > We have a very fresh gluster 3.10.10 installation. > Our volume

Hello, We have a very fresh gluster 3.10.10 installation. Our volume is created as distributed volume, 9 bricks 96TB in total (87TB after 10% of gluster disk space reservation) For some reasons I can?t ?heal? the volume: # gluster volume heal gv0 Launching heal operation to perform index self heal on volume gv0 has been unsuccessful on bricks that are down. Please check if all brick processes

After discussing with Xavi in #gluster-dev we found out that we could eliminate the slow lstats by disabling disperse.eager-lock. There is an open issue here : https://bugzilla.redhat.com/show_bug.cgi?id=1546732 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180226/77e194f8/attachment.html>

Hello fellow community members! I just joined you in order to find an information about how to start using Puppet... Currently we use cfengine for our legacy system containing several OS platforms, including physical and virtual servers. For fresh new hardware and OS versions we decided to go with Puppet due to it''s growing popularity (wow, 4082 members of this group only!).

Hi, Here are some top reminders for the 3.12 release: 1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged to prepare for the same as per the calendar posted here. 2) 3.12 is a long term maintenance (LTM) release, and potentially the last in the 3.x line of Gluster! 3) From this release onward, the feature freeze date is moved ~45 days in advance, before the release.

Hello. After working with the 3.12 flavor of gluster I learned nfs-ganesha was replaced with storhaug in 3.11.Have people been successfully utilizing storhaug and does any documentation exist for using it in a ha nfs configuration or is ha in gluster so rarely used it's a non-issue for most gluster users? Going through the lists, it was recommended in November to not use storhaug and if

Hello, all! Suddenly, after upgrading of my FreeBSD-Stable box I got message from VMWare: VMware Workstation PANIC: BUG F(571):1607 bugNr=2302. Anybody can help me to fix this bug? (I tryed back to 4.8-release but it didn't help ...) Best regards, Anatoliy Dmytriyev

On 20/12/2017 16:51, Craig Lesle wrote: > With the release of 3.12 ltm and now 3.13 stm, when 4.0 is > released 3.10 is shown to be at eol; > > Version Status ???? Release_Date? EOL_Version EOL_Date > 3.10 ?? LTM ??? ??? 2017-02-27 ?? 4.0 ??? > 3.11 ?? EOL ??? ??? 2017-05-30 ?? 3.12 ??? ?? 2017-8-30 > 3.12 ?? LTM ??? ??? 2017-08-30??? 4.3 ??? > 3.13 ?? STM ??? ???

On 01/06/17 22:47, Shyam wrote: > Hi, > > Here are some top reminders for the 3.12 release: > > 1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged > to prepare for the same as per the calendar posted here. > > 2) 3.12 is a long term maintenance (LTM) release, and potentially the > last in the 3.x line of Gluster! > > 3) From this release

I auto-upgraded puppet (as usual) using "yum upgrade -y", and now all agents are getting error 400. # puppet --version 3.0.0 On agent (any!) # puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for build6.[censored]: Failed to find facts from PuppetDB at abyss.[censored]:8081:

09.04.2018 16:18, Ravishankar N ?????: > > > On 04/09/2018 05:40 PM, mabi wrote: >> Again thanks that worked and I have now no more unsynched files. >> >> You mentioned that this bug has been fixed in 3.13, would it be >> possible to backport it to 3.12? I am asking because 3.13 is not a >> long-term release and as such I would not like to have to upgrade

Hello All, I was wondering how I can get the overall Pearson chi^2 test of model fit with its df and p value in the LTM package for the 2PL models. Thanks, -- Davood Tofighi Department of Psychology Arizona State University [[alternative HTML version deleted]]

Afternoon R help, I want to run Rasch/IRT analyses using the ltm package, however, I am using large scale survey data which requires weighting for accurate results. I attempted to create a weighted object to insert into the formulae of the ltm packages, however, the survey data only includes 30 replicate weights and a sampling weight. The svrepdesign requires additional information such as

Hello all fellow GlusterFriends, I would like you to comment / correct my upgrade procedure steps on replica 2 volume of 3.7.x gluster. Than I would like to change replica 2 to replica 3 in order to correct quorum issue that Infrastructure currently has. Infrastructure setup: - all clients running on same nodes as servers (FUSE mounts) - under gluster there is ZFS pool running as raidz2 with SSD