Cisco Bug: CSCuj87441 - Database catalog is not read based on delivery service
Jun 21, 2020
- Cisco Content Delivery Engine Series
Known Affected Releases
Symptom: When multiple delivery services are assigned to a multicast cloud, each of them have a crawl job scheduled the following scenario may be observed. 1. Jobs are being scheduled only for a single delivery service . The scheduling for this delivery service must have stopped after reaching the delivery service max-limit, but there are sessions available at cloud level and still files for other delivery service are not scheduled. However if the DB catalog reading fetches records for other delivery service files , they will be seen scheduling. Conditions: The delivery service appearing to be preferred must have had it's crawl job done first, making all the files ready for distribution before other delivery service files. The DB catalog record reads the catalog table based on total global max Job count. Now this might be retrieving records belonging to the same delivery service. This problem will be seen if there are too many files in a single crawl job. The starvation for other delivery service exists in previous releases.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases