---
**[tickets:#3401] amf: CSI removal is sequential even when CSIs are at the same
rank within an SI**
**Status:** unassigned
**Milestone:** 5.27.01
**Created:** Thu Jun 18, 2026 10:46 AM UTC by Thang Duc Nguyen
**Last Updated:** Thu Jun 18, 2026 10:46 AM UTC
**Owner:** nobody
Currently when amfnd removes CSI assignments from an SI, it removes CSIs one at
a time sequentially — even when multiple CSIs are at the same rank (no CSI
dependencies between them). The removal only proceeds to the next CSI after the
previous component responds to the CSI Remove callback.
For example, with 5 CSIs at the same rank assigned to 5 different components,
if each component takes 2s to respond to the CSI Remove callback, the total
removal time is ~10s (5 x 2s sequential). Since these CSIs have no dependency
relationship, they can safely be removed in parallel, reducing the total time
to ~2s.
This sequential behavior affects:
1. SI lock operations (amf-adm lock <SI>).
2. SU lock operations (amf-adm lock <SU>).
3. Node shutdown (systemctl stop opensafd).
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
