Prioritized Queue System for Event Processing

Data Hub

What’s new?

Bullhorn is introducing a new prioritization system for event processing to handle high-volume data entities better. It addresses processing delays experienced during periods of intense activity when many events generate in a short timeframe. When enabled, an additional log entry will appear, indicating that deprioritized records are being processed along with the expected number of records:

Sending deprioritized entity data sync objects to separate thread pool

Key changes include:

• A dedicated thread pool for processing lower-priority, high-volume entity events.

• Configurable entity prioritization to manage resource allocation.

• An enhanced system stability during peak processing periods.

Why does it matter?

The new system preserves processing capacity for mission-critical events during high-volume periods and maintains system responsiveness during activity bursts. It also reduces overall event processing backlog and ensures high-priority reporting workflows remain unaffected.

How do I enable this?

By default, Data Hub Data (EdsData) is included in the deprioritized list. You can manage the list of entities by modifying the application.properties file, such as:

batchDataEventProcessingByEntity=true

deprioritized.entities=[comma delimited list of entities]