Application Server Administration job failed

Problem
CPU 99%.
User Profile Synchronization is stuck on Running.
SharePoint Timer Service is eating up the whole CPU and the event viewer says:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by xxxxxxxx, in the OWSTIMER process, on machine xxxxxxx.  View the tracing log for more information about the conflict.

Technical Support Details:
Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by xxxxxxxx, in the OWSTIMER process, on machine xxxxxxx. View the tracing log for more information about the conflict.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

This issue occurs if the contents of the file system cache on the front end servers are newer than the contents of the configuration database.

Fix the problem
Manually clear the file system cache on the local servers (fe's) on which the timer service is running (KB)

• Stop the SharePoint Timer Service in Administrative Tool/Services.
• Go to the cache folder. For Windows Server 2008: Drive:\ProgramData\Microsoft\SharePoint\Config
• Find the folder that contains the file Cache.ini
• Delete all the XML configuration files in the folder so that you can verify that the folder is replaced by new XML files when the cache is rebuilt. 
• Open the Cache.ini file, delete all content in the file and type 1, save and exit. 
• Start the SharePoint Timer service 

The file system cache should now have been recreated. Make sure that you perform this procedure on all servers in the server farm.
Make sure that the Cache.ini file in the folder now contains the previous value. For example, make sure that the value of the Cache.ini file is not 1.