Cause
A contact or roster is a concrete relationship where one user, also known as a watcher, wants to see the presence of another user presentity, and indirectly requires allocation of system resources. The number of contacts or rosters on the system can impact the system performance. This health check monitors whether the system has too many contacts or rosters and advises the administrator to take action.
Solution
- If this alarm is raised, the administrator must examine the report logs on the roster.
ADDITIONAL INFORMATION:
For example, Current Roster Statistics is:
Where:
x is the total number allowed by the system and is only impacted by the number of users.
y is the number of rosters allocated from system resources based on the number of provisioned users (y% is a percentage of y from x).
z is the actual number of rosters (actual presence relationships) created on the system (z% is percent of z from x).
ADDITIONAL INFORMATION:
If z exceeds x, then there are too many rosters created. Increase the overall capacity of the system by adding more virtual machines to allow the system to support more users. Then, you can request the users to reduce the number of presence contacts in their contact list.
If y exceeds x, then the system is in danger of exceeding the resources if every user creates their maximum number of contacts. Increase the overall capacity of the system by adding more virtual machines to allow the system to support more users. Then, you can reduce the value of the Roster Limit: Maximum Number of Contacts and Roster Limit: Maximum Number of External Watchers service attributes.
For more information, see Configuring Roster Limit
and Configuring number of users for a Presence Services cluster.
