[gpfsug-discuss] Why cluster-wide locks for firmware-updates and the like

[Jan-Frode Myklebust]

These locks seems a bit excessive.. even blocking for mmstartup, which
means a node can’t join the cluster for hours during enclosure updates.


 -jf

fre. 30. jun. 2023 kl. 22:59 skrev Steve Duersch <duersch at us.ibm.com>:

> This behavior is expected.   A cluster wide lock is necessary because
> mmchfirmware itself will update the cluster as a whole during this
> process.   So, there shouldn't be a need to run updates elsewhere at the
> same time.
>
>
>
> Steve Duersch
>
> IBM Storage Scale/Storage Scale System
>
> 845-433-7902
>
> IBM Poughkeepsie, New York
>
>
> ------------------------------
>
>
>
>
>
> Hi
>
>
>
> If you are doing it offline (which for bigger setups) and pass the class or CSV of nodes, it is done in parallel in all nodes.
>
>
>
> For your request I think there is a RFE (not sure public or not) already created, but I don’t disagree would be nice improvement to lock at the single BB
>
>
>
> --
>
> Ystävällisin terveisin/Regards/Saludos/Salutations/Salutacions
>
>
> <https://www.google.com/maps/search/Toinen+linja+7+%0D%0A+00530+Helsinki+%0D%0A+Uusimaa+-+Finland?entry=gmail&source=g>
>
> Luis Bolinches
>
>
> <https://www.google.com/maps/search/Toinen+linja+7+%0D%0A+00530+Helsinki+%0D%0A+Uusimaa+-+Finland?entry=gmail&source=g>
>
> Executive IT Specialist
>
> IBM Storage Scale development
>
> Phone: +358503112585
>
>
>
> Ab IBM Finland Oy
>
> Toinen linja 7 <https://www.google.com/maps/search/Toinen+linja+7+%0D%0A+00530+Helsinki+%0D%0A+Uusimaa+-+Finland?entry=gmail&source=g>
>
> 00530 Helsinki <https://www.google.com/maps/search/Toinen+linja+7+%0D%0A+00530+Helsinki+%0D%0A+Uusimaa+-+Finland?entry=gmail&source=g>
>
> Uusimaa - Finland <https://www.google.com/maps/search/Toinen+linja+7+%0D%0A+00530+Helsinki+%0D%0A+Uusimaa+-+Finland?entry=gmail&source=g>
>
>
>
> Visitors entrance: Siltasaarenkatu 22 <https://www.google.com/maps/search/Siltasaarenkatu+22?entry=gmail&source=g>
>
>
>
> "If you always give you will always have" --  Anonymous
>
>
>
> https://www.credly.com/users/luis-bolinches/badges
>
>
>
> -----Original Message-----
>
> From: gpfsug-discuss <gpfsug-discuss-bounces at gpfsug.org <http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org>> On Behalf Of Hannappel, Juergen
>
> Sent: Tuesday, 27 June 2023 19.07
>
> To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org <http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org>>
>
> Subject: [EXTERNAL] [gpfsug-discuss] Why cluster-wide locks for firmware-updates and the like
>
>
>
> Moin,
>
> when e.g doing mmchfirmware there is a cluster-wide lock preventing me from running mmchfirmware on several building blocks at once, while I would assume that only within one building block a lock is needed.
>
> Why is that so? Can that be changed in a future release?
>
>
>
> Also some apparently cluster wide locks create false alarms when checking for the recovery group status on one building block is blocked by some actions on another one...
>
>
>
> --
>
> Dr. Jürgen Hannappel  DESY/IT    Tel.  : +49 40 8998-4616
>
>
>
> _______________________________________________
>
> gpfsug-discuss mailing list
>
> gpfsug-discuss at gpfsug.org
>
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>
>
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at gpfsug.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20230630/23fdad3d/attachment.htm>