[Gluster-users] Version uplift query
Amudhan P
amudhan83 at gmail.com
Thu Feb 28 06:10:36 UTC 2019
Hi Poornima,
Instead of killing process stopping volume followed by stopping service in
nodes and update glusterfs.
can't we follow the above step?
regards
Amudhan
On Thu, Feb 28, 2019 at 8:16 AM Poornima Gurusiddaiah <pgurusid at redhat.com>
wrote:
>
>
> On Wed, Feb 27, 2019, 11:52 PM Ingo Fischer <ingo at fischer-ka.de> wrote:
>
>> Hi Amar,
>>
>> sorry to jump into this thread with an connected question.
>>
>> When installing via "apt-get" and so using debian packages and also
>> systemd to start/stop glusterd is the online upgrade process from
>> 3.x/4.x to 5.x still needed as described at
>> https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/ ?
>>
>> Especially because there is manual killall and such for processes
>> handled by systemd in my case. Or is there an other upgrade guide or
>> recommendations for use on ubuntu?
>>
>> Would systemctl stop glusterd, then using apt-get update with changes
>> sources and a reboot be enough?
>>
>
> I think you would still need to kill the process manually, AFAIK systemd
> only stops glusterd not the other Gluster processes like
> glusterfsd(bricks), heal process etc. Reboot of system is not required, if
> that's what you meant by reboot. Also you need follow all the other steps
> mentioned, for the cluster to work smoothly after upgrade. Especially the
> steps to perform heal are important.
>
> Regards,
> Poornima
>
>
>> Ingo
>>
>> Am 27.02.19 um 16:11 schrieb Amar Tumballi Suryanarayan:
>> > GlusterD2 is not yet called out for standalone deployments.
>> >
>> > You can happily update to glusterfs-5.x (recommend you to wait for
>> > glusterfs-5.4 which is already tagged, and waiting for packages to be
>> > built).
>> >
>> > Regards,
>> > Amar
>> >
>> > On Wed, Feb 27, 2019 at 4:46 PM ABHISHEK PALIWAL
>> > <abhishpaliwal at gmail.com <mailto:abhishpaliwal at gmail.com>> wrote:
>> >
>> > Hi,
>> >
>> > Could you please update on this and also let us know what is
>> > GlusterD2 (as it is under development in 5.0 release), so it is ok
>> > to uplift to 5.0?
>> >
>> > Regards,
>> > Abhishek
>> >
>> > On Tue, Feb 26, 2019 at 5:47 PM ABHISHEK PALIWAL
>> > <abhishpaliwal at gmail.com <mailto:abhishpaliwal at gmail.com>> wrote:
>> >
>> > Hi,
>> >
>> > Currently we are using Glusterfs 3.7.6 and thinking to switch on
>> > Glusterfs 4.1 or 5.0, when I see there are too much code changes
>> > between these version, could you please let us know, is there
>> > any compatibility issue when we uplift any of the new mentioned
>> > version?
>> >
>> > Regards
>> > Abhishek
>> >
>> >
>> >
>> > --
>> >
>> >
>> >
>> >
>> > Regards
>> > Abhishek Paliwal
>> > _______________________________________________
>> > Gluster-users mailing list
>> > Gluster-users at gluster.org <mailto:Gluster-users at gluster.org>
>> > https://lists.gluster.org/mailman/listinfo/gluster-users
>> >
>> >
>> >
>> > --
>> > Amar Tumballi (amarts)
>> >
>> > _______________________________________________
>> > Gluster-users mailing list
>> > Gluster-users at gluster.org
>> > https://lists.gluster.org/mailman/listinfo/gluster-users
>> >
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> https://lists.gluster.org/mailman/listinfo/gluster-users
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190228/35c1e3c7/attachment.html>
More information about the Gluster-users
mailing list