For Web 8.5, bulk publishing fails with error "Command deserialization failed for file"

- When bulk publishing 20-30 pages, 10-30% of these would fail to successfully publish. If an admin would then publish these pages singularly, then the pages would successfully publish.
- Errors in Deployer log such as the below

ERROR FSLocationPoller - Queue [Id=ContentQueue]. Command deserialization failed for file 
'DEPLOYER_QUEUE_FILEPATH\ContentQueue\tcm_0-517888-66560.Content.json'. File not found, not accessible, or corrupt
java.nio.file.NoSuchFileException: DEPLOYER_QUEUE_FILEPATH\queue\ContentQueue\tcm_0-517888-66560.Content.json
    at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
    at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
2020-06-16 07:07:29,293 ERROR FSBinaryStorage - Tried to remove non-existing file 'tcm_0-517919-66560+Tridion-Process-Deploy+TaxonomyDeploy+TransactionLog_TaxonomyDeploy'.
java.nio.file.NoSuchFileException: DEPLOYER_FILEPATH\binary\Binaries\tcm_0-517919-66560+Tridion-Process-Deploy+TaxonomyDeploy+TransactionLog_TaxonomyDeploy

- 2 load balanced CMS servers in this environment.


 

Actions taken were:
- 1500+ .state files were removed from the two CMS servers, as discussed in KB article SDL Web - How to cleanup files left over by publishing
- Several .busy files were removed from the Deployer incoming folders.
- State Store DB tables had thousands of rows related to past publishing transactions, as in below example.  These were removed as discussed in KB article For Tridion Sites 9.1 and earlier versions, how to remove unnecessary data in the state store database? 
* 3500+ rows were removed from the EXECUTION table
* 18000+ rows were removed from the EXECUTION_PROPERTY table
* 16000+ rows were removed from the PIPELINE table
* 43000+ rows were removed from the STEP table.

After actions, bulk publishing could be completed successfully.  Customer was further advised to apply the latest Deployer hotfix as their current Deployer was relatively old, and also review and tune environment as discussed in KB article For Web 8.5, how to tune the Publisher and Deployer?