If the Publishing Queue shows the item stuck at Waiting for Deployment
The 'Waiting for Deployment' message means that the item is waiting to be deployed, and is currently in the Content Deployer queue.
This typically happens if your configured window size (WindowSize in the Content Deployer configuration file, cd_deployer_conf.xml) is more than 2 times the number of deployment threads (Workers in the Content Deployer configuration file).
The value of Workers depends on the number of CPU cores on your server, and if this number is too low compared to the window size you configured, items will be placed in the queue.
Normally, this simply means that deployment is not immediate, but if you see many items in this state, or the same item stuck in this state for an unacceptably long time, too many items are being sent to the Content Deployer, and a Throttled state is likely to occur.
To resolve a persistent Waiting for Deployment state, do one of the following:
- Increase the number of workers. This increases CPU load and may require a hardware upgrade (more CPU cores).
- Decrease the total number of Publisher threads (configured as the
TransportPriorityPoolSizeattribute of theWorkerselement) in the Transport Service, cd_transport_conf.xml.
Another, less frequent, reason why items might remain in this state is because the Cache Channel Service has somehow become unavailable after the Content Deployer has started. For example, a network error may make the Cache Channel Service go offline.
In this case, the Content Deployer becomes stuck when the number of items to deploy exceeds the size of the event queue of the cache (configured in your Storage Layer configuration file, cd_storage_conf.xml, in the Queuesize attribute of the RemoteSynchronization element, defaults to 128). The Content Deployer remains stuck even if the Cache Channel Service becomes available again.
Monitoring your Cache Channel Service is the easiest way to catch such an outage as soon as it occurs. In this case, you may even be able to bring your Cache Channel Service back up before the queue fills up.
Alternatively, you can see whether this is the case by checking your Content Deployer log for the following reoccurring message:
DEBUG CacheChannel - No slot available in event processing queue, waiting for available slot
To resolve this issue, restart your Content Deployer.