After restart of the instance, unprocessed records might get stuck in the Generic Processing Pool and never get picked up, which might lead to the Path Analyzer not displaying data.
This issue can also cause increased resource consumption on the xDB pools database. In Azure SQL environments, this might be observed as high DTU usage. In SQL Server environments, this might be observed as high CPU usage.
The increased resource consumption can be caused by repeated execution of the following SQL query against the [xdb_processing_pools].[GenericProcessingPool] table:
UPDATE TOP (@Size)
[xdb_processing_pools].[GenericProcessingPool]
SET
[Scheduled] = DATEADD( SECOND, @Timeout, @Now ),
[Attempts] = ([Attempts] + 1),
@Retry = 0
OUTPUT
INSERTED.[Id] AS [Id],
INSERTED.[Created] AS [Created],
DELETED.[Scheduled] AS [Scheduled],
INSERTED.[Attempts] AS [Attempts],
INSERTED.[Properties] AS [Properties]
WHERE
([Pool] = @Pool) AND
([Scheduled] <= @Now)
To resolve this issue, consider one of the following options:
Be aware that the hotfixes were built for the specific Sitecore XP versions and must not be installed on other Sitecore XP versions or in combination with other hotfixes. If any other hotfixes have already been installed on a certain Sitecore XP instance, send a request for a compatibility check to Sitecore Support.
Note that you must extract the ZIP file contents to locate installation instructions and related files inside. You must install the hotfix on a CM instance and then sync it with other instances using standard development practices.