similar to: upgrade from 3.8.12 to 3.9.x - to do or...

Hi Kaleb, Thanks, this refers to 3.11.x On Mon, Jul 3, 2017 at 4:16 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > >> On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >>> >>> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >>> >>> Hello Atin,

On 01/02/2018 11:03 PM, Vijay Bellur wrote: > ... > The people who were writing storhaug never finished it. Keep using > 3.10 until storhaug gets finished. > > > > Since 3.10 will be EOL in approximately 2 months from now, what would be > our answer for NFS HA if storahug is not finished by then? > > ?-? ?Use ctdb > ?-? ?Restore nfs.ganesha CLI

Thanks Jiffin, Btw, the nfs-ganesha part in the release notes is having a wrong header, so it's not highlighted. One thing that it is still mystery to me: gluster 3.8.x does all what the release notes of 3.9 says - automatically. Any chance that someone could port it to 3.9? Thanks for the links On Wed, Dec 6, 2017 at 7:28 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote: >

On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >> >> Hello Atin, >> >> I've gotten around to this and was able to get upgrade done using >> 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't

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

On 07/03/2017 04:34 AM, Atin Mukherjee wrote: > > On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: > > Hello Atin, > > I've gotten around to this and was able to get upgrade done using > 3.7.0 before moving to 3.11. For some reason 3.7.9 wasn't working well. > > On 3.11 though I notice that gluster/nfs is really

On 13/09/17 06:21, Gaurav Yadav wrote: > Please provide the output of gluster volume info, gluster > volume status and gluster peer status. > > Apart? from above info, please provide glusterd logs, > cmd_history.log. > > Thanks > Gaurav > > On Tue, Sep 12, 2017 at 2:22 PM, lejeczek > <peljasz at yahoo.co.uk <mailto:peljasz at yahoo.co.uk>> wrote:

Thanks Kaleb, I presumed as much. I did previously try with 3.10 but ended up running into issues with pacemaker. I guess same question applied, can you point to any guides to a full setup of Ganesha on 3.10? Thanks From: Kaleb S. KEITHLEY <kkeithle at redhat.com> To: Jonathan Archer <jf_archer at yahoo.com>; "gluster-users at gluster.org" <gluster-users at

Please send me the logs as well i.e glusterd.logs and cmd_history.log. On Wed, Sep 13, 2017 at 1:45 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > > > On 13/09/17 06:21, Gaurav Yadav wrote: > >> Please provide the output of gluster volume info, gluster volume status >> and gluster peer status. >> >> Apart from above info, please provide glusterd logs,

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 ??? ???

After 3.10 you'd need to use storhaug.... Which.... doesn't work (yet). You need to use 3.10 for now. On 07/06/2017 12:53 PM, Anthony Valentine wrote: > I'm running this on CentOS 7.3 > > [root at glustertest1 ~]# cat /etc/redhat-release > CentOS Linux release 7.3.1611 (Core) > > > Here are the software versions I have installed. > > [root at

On 06/19/2017 07:28 PM, Lindsay Mathieson wrote: > On 18/06/2017 12:47 PM, Lindsay Mathieson wrote: >> I installed 3.8.12 a while back and the packages seem to have been >> updated since (2017-06-13), prompting me for updates. >> >> >> I haven't seen any release announcements or notes on this though. > > > > Bump - new versions are 3.8.12-2.

Thanks Kaleb, indeed, starting ganesha without HA works, but it's certainly not desirable, and everything is back to manual operations like in the old days. Do you have any time estimate for storhaug to be ready? Maybe it's worth to mention this in the documentation of 3.12 as well, otherwise other people will have the same problems. Cheers, ??? Alessandro Il 12/09/17 14:48,

Yes it could as depending on number of bricks there might be too many brick ops involved. This is the reason we introduced --timeout option in CLI which can be used to have a larger time out value. However this fix is available from release-3.9 onwards. On Mon, Jul 24, 2017 at 3:54 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > hi fellas > > would you know what could be the

Currently running 3.8.12, planning to rolling upgrade it to 3.8.15 this weekend. * debian 8 * 3 nodes * Replica 3 * Sharded * VM Hosting only The release notes strongly recommend upgrading to 3.10 * Is there any downside to staying on 3.8.15 for a while longer? * I didn't see anything I had to have in 3.10, but ongoing updates are always good :( This mildly concerned me:

Additionally the brick log file of the same brick would be required. Please look for if brick process went down or crashed. Doing a volume start force should resolve the issue. On Wed, 13 Sep 2017 at 16:28, Gaurav Yadav <gyadav at redhat.com> wrote: > Please send me the logs as well i.e glusterd.logs and cmd_history.log. > > > On Wed, Sep 13, 2017 at 1:45 PM, lejeczek

hi fellas would you know what could be the problem with: vol status detail times out always? After I did above I had to restart glusterd on the peer which had the command issued. I run 3.8.14. Everything seems to work a ok. many thanks L.

Executing "gluster volume set all cluster.op-version <op-version>"on all the existing nodes will solve this problem. If issue still persists please provide me following logs (working-cluster + newly added peer) 1. glusterd.info file from /var/lib/glusterd from all nodes 2. glusterd.logs from all nodes 3. info file from all the nodes. 4. cmd-history from all the nodes. Thanks

On 11/21/2017 08:59 AM, Jonathan Archer wrote: > Hi all, > > I've just installed gluster 3.12 to build a test NFS storage cluster and > noticed that ganesha seems to have been consumed into storhaug. > > Is there any documentation or guides around for storhaug? > No, not yet. If you want HA clustered ganesha with glusterfs your best bet for now is to use

1) one peer, out of four, got separated from the network, from the rest of the cluster. 2) that unavailable(while it was unavailable) peer got detached with "gluster peer detach" command which succeeded, so now cluster comprise of three peers 3) Self-heal daemon (for some reason) does not start(with an attempt to restart glusted) on the peer which probed that fourth peer. 4) fourth