- **status**: review --> fixed
- **Comment**:
commit 07cf0d60d28cf0282cdcb1bba8c231bc1f683c42 (HEAD -> develop,
origin/develop, ticket-3268)
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Wed Jul 28 16:18:01 2021 +0700
imm: update README file for a new attribute [#3268]
commit 52d314be58be0543ff635fe39e805f6367085b61
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Wed Jul 28 10:31:38 2021 +0700
imm: add test case of saImmSyncrTimeout attribute [#3268]
Adding 5 new test case into a testsuite 6
commit a86cb14de9a263a23d7caef5c9483ca570f363ba
Author: thien.m.huynh <thien.m.hu...@dektech.com.au>
Date: Sat Jul 24 14:26:13 2021 +0700
imm: Introduce a configurable attribute saImmSyncrTimeout [#3268]
In a large cluster size, it is impossible to adjust MDS wait time for all
clients in cluster by change IMMA_SYNC_TIMEOUT environment variable.
Because technique environment variable needs to restart to apply the changed
variable and it is a time-consuming.
This ticket introduce a configurable attribute `saImmSyncrTimeout`
to `SaImmMngt` class, that distribute the new timeout to all IMM clients
and force them to use the new timeout. If user deletes value of attribute
`saImmSyncrTimeout`, it will go back to default value (0). And it is will
keep backward compatible with IMMA_SYNC_TIMEOUT technique.
In default, this feature is disabled.
Correct value of variable environment IMMA_SYNCR_TIMEOUT when set a value
less than 10 will only be interpreted as the value 10.
---
** [tickets:#3268] imm: New admin op to force IMM Agent using new timeout
value**
**Status:** fixed
**Milestone:** 5.21.10
**Created:** Mon Jun 21, 2021 01:02 AM UTC by Minh Hon Chau
**Last Updated:** Fri Jul 30, 2021 01:58 AM UTC
**Owner:** Thien Minh Huynh
This ticket is created in conjunction with #3260, in which the single step
upgrade fails due to a lot of component timeout.
The IMMA_SYNC_TIMEOUT technically environment variable can be exported with
appropriate value in each components on every nodes; however, if the cluster
has several nodes, each of which has hundreds of components, that make
IMMA_SYNC_TIMEOUT update difficult in live site.
This ticket introduces a configurable attribute to distribute the new timeout
to all IMM clients and force them to use the new timeout.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
