[Gluster-users] About the maintenance time

[Ravishankar N]

On 06/16/2017 09:07 AM, te-yamauchi at usen.co.jp wrote:
> I currently use it in the replica configuration of 3.10.2.
> The brick process may not start when restarting the storage server. Also, when using gnfs, the I / O may hang up and become unusable.
> After checking the release notes of 3.11.0, the following ID seems to be applicable, so please reflect it if it can be reflected in 3.10 series. Also, for items with high urgency
> Since 3.11.0 has just been released and it is a short-term release version, I want to avoid upgrading at this stage.
3.11 is short term but the End Of Life for it is the same as that for  
3.8 and 3.10, i.e. when 3.12 is released.
>
> Bug 1418014 - disable client.io-threads on replica volume creation
> Bug 1421937 - [Replicate] "RPC call decoding failed" leading to IO hang & mount inaccessible
> Bug 1427012 - Disconnects in nfs mount leads to IO hang and mount inaccessible
> Bug 1430860 - brick process crashes when glusterd is restarted
> Bug 1449933 - Brick Multiplexing :- resetting a brick bring down other bricks with same PID
The patches for these bugs seem to be:
glusterd : do not load io-threads in client graph for replicate volumes
rpcsvc: Add rpchdr and proghdr to iobref before submitting to transport
rpc/clnt: remove locks while notifying CONNECT/DISCONNECT
glusterfsd+libglusterfs: add null checks during attach
glusterd: Make reset-brick work correctly if brick-mux is on

I'm CC'ing the respective patch authors for deciding on if these patches  
warrant a backport for 3.8/3.10 (or if they are already present.)

Thanks,
Ravi
> Thank you.
>
>> On 06/15/2017 12:26 PM, te-yamauchi at usen.co.jp wrote:
>>> What is the current stable version of glusterfs?
>> 3.8.x and 3.10.x are long term stable releases. Newer features are in 3.11.x,
>> which is  a short term stable release branch.
>>> Also, the current latest versions are 3.8.9, 3.10.3, and 3.11.0, respectively, but
>> why the bug-fixed contents in 3.11.0 are not applied to 3.8 series and 3.10
>> series? Do you apply with the next minor version upgrade?
>> Ideally they should be. Sometimes developers are busy and might miss out on
>> back porting the bug-fixes to all release branches. If there is a specific bug fix
>> patch from 3.11 that you want in 3.8/3.10, just ask over here. You can also help
>> out  by sending the back ports yourself.
>>
>> Release schedule: https://www.gluster.org/community/release-schedule/
>> Back porting guidelines:
>> https://gluster.readthedocs.io/en/latest/Developer-guide/Backport-Guidelin
>> es/
>> -Ravi
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-users