- **assigned_to**: A V Mahesh (AVM) --> nobody
- **Blocker**: --> False
---
** [tickets:#1815] mds: suspected message loss in large cluster deployments**
**Status:** assigned
**Milestone:** future
**Created:** Mon May 09, 2016 06:45 AM UTC by Gary Lee
**Last Updated:** Tue Nov 15, 2016
- **status**: unassigned --> assigned
- **assigned_to**: A V Mahesh (AVM)
---
** [tickets:#1815] mds: suspected message loss in large cluster deployments**
**Status:** assigned
**Milestone:** 5.0.2
**Created:** Mon May 09, 2016 06:45 AM UTC by Gary Lee
**Last Updated:** Tue Sep 20, 2016 05:44
- **Milestone**: 5.0.1 --> 5.0.2
---
** [tickets:#1815] mds: suspected message loss in large cluster deployments**
**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Mon May 09, 2016 06:45 AM UTC by Gary Lee
**Last Updated:** Fri May 13, 2016 05:56 AM UTC
**Owner:** nobody
It has been
in the osafclmd trace file, amfd is initialising with clmd:
Apr 27 22:29:47.391760 osafclmd [9595:clms_evt.c:0252] >> clms_client_new: MDS
dest 2010fde2420f8
Apr 27 22:29:47.391765 osafclmd [9595:clms_evt.c:0278] << clms_client_new:
client_id 1
later on, amfd request CLM tracking
Apr 27
- **Milestone**: 4.7.2 --> 5.0.1
---
** [tickets:#1815] mds: suspected message loss in large cluster deployments**
**Status:** unassigned
**Milestone:** 5.0.1
**Created:** Mon May 09, 2016 06:45 AM UTC by Gary Lee
**Last Updated:** Fri May 13, 2016 05:49 AM UTC
**Owner:** nobody
It has been
Workaround the problem by calling avd_clm_track_start() after
avd_imm_config_get() is completed
changeset: 7633:073d00b1cb8f
branch: opensaf-5.0.x
tag: tip
parent: 7630:bf51ccd1c73d
user:Gary Lee
date:Fri May 13 15:41:44 2016 +1000
- **summary**: amf: heartbeat timeout on large clusters --> mds: suspected
message loss in large cluster deployments
- Description has changed:
Diff:
--- old
+++ new
@@ -1,4 +1,6 @@
-On large clusters (75 nodes tested in this case), avd_imm_config_get() can
take up to 3 minutes to