- **status**: review --> fixed
- **Comment**:
commit eaf187e9a04ee147dacee8d722c09aecf9a52426
Author: Minh Chau <[email protected]>
Date: Tue May 18 14:41:59 2021 +1000
imma: Correctly use IMMA_SYNCR_TIMEOUT [#3260]
commit fa8325e924060496184cb57e43bd7eff3bb71a84
Author: Minh Chau <[email protected]>
Date: Tue May 18 14:41:59 2021 +1000
immnd: Make IMMSV_FEVS_MAX_PENDING environment variable [#3260]
---
** [tickets:#3260] immnd: many clients timeout on the imm api calls**
**Status:** fixed
**Milestone:** 5.21.06
**Created:** Wed May 05, 2021 12:27 AM UTC by Minh Hon Chau
**Last Updated:** Mon May 17, 2021 11:53 PM UTC
**Owner:** Minh Hon Chau
In a large cluster (24 nodes), the components have very often been timeout in
their imm api calls. This timeout results in a component restart. During single
step upgrade, due to the imm timeout, the amf locking nodegroup operation fails
because of many component restarts escalated to node failover, etc... This
ticket suggests IMMSV_DEFAULT_FEVS_MAX_PENDING and IMMSV_WAIT_TIME to be
environment variables so the components can adjust these parameters according
to the size of cluster.
---
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
