High CPU usage after you publish a changed topology in Lync Server 2013 that has the Response Group Service run

Symptoms

This issue occurs when you make a major change to a Lync topology (for example, adding or removing a server) and then you publish the topology in a Microsoft Lync Server 2013 environment that has the Response Group Service run.

When this issue occurs, the LyncIntFeature or the LyncExtFeature application pool on the Lync Server 2013 front-end server consumes large amounts of CPU resources.

Cause

This issue occurs because the topology snapshot was recomputed multiple times by the Response Group Service.

Resolution

To resolve this issue, install the September 2015 cumulative update 5.0.8308.933 for the Lync Server 2013 Response Group service.

Note This update redesigns and optimizes the computation of the topology snapshot.
Ιδιότητες

Αναγνωριστικό άρθρου: 3083355 - Τελευταία αναθεώρηση: 2 Οκτ 2015 - Αναθεώρηση: 1

Σχόλια