- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -2,7 +2,4 @@
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:
-
-- an IMM admin operation to possibly distribute the new timeout to all IMM
agents and force them to use the new timeout.
-- an IMM admin operation to restore the timeout to old value.
+This ticket introduces a configurable attribute to distribute the new
timeout to all IMM clients and force them to use the new timeout.
~~~~
- **status**: accepted --> review
---
** [tickets:#3268] imm: New admin op to force IMM Agent using new timeout
value**
**Status:** review
**Milestone:** 5.21.10
**Created:** Mon Jun 21, 2021 01:02 AM UTC by Minh Hon Chau
**Last Updated:** Mon Jun 28, 2021 04:30 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 [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
