|
|
Last revision
Both sides next revision
|
devel:documentation:adm:configuration:events [2019/03/01 08:39]
kotisovam created parts moved from devel section |
devel:documentation:adm:configuration:events [2019/04/26 09:32]
tomiskar [Features] |
| Before event is persisted into queue, then event priority is evaluated, priority types: | Before event is persisted into queue, then event priority is evaluated, priority types: |
| * ''IMMEDIATE'' - immediate ~ synchronously. Event will be executed synchronously. | * ''IMMEDIATE'' - immediate ~ synchronously. Event will be executed synchronously. |
| * ''HIGH'' - asynchronously (7 / 10 in one cycle) | * ''HIGH'' - asynchronously (7 / 10 in one cycle, batch size can be [[..:..:application_configuration:dev:backend#entity_events|configured]]) |
| * ''NORMAL'' - asynchronously (3 / 10 in one cycle) | * ''NORMAL'' - asynchronously (3 / 10 in one cycle, batch size can be [[..:..:application_configuration:dev:backend#entity_events|configured]]) |
| |
| Priority can be set to event manually or registered processors can vote about event's priority - see [[#asyncentityeventprocessor|AsyncEntityEventProcessor]] - the highest priority is used. | Priority can be set to event manually or registered processors can vote about event's priority - see [[#asyncentityeventprocessor|AsyncEntityEventProcessor]] - the highest priority is used. |
| * original source (embedded dtos and audit fields are ignored). | * original source (embedded dtos and audit fields are ignored). |
| |
| Older duplicate events are removed - the newest event is used. Events are processed by priority in bulk, default bulk size is **100 events** => duplicates are removed only in this bulk (not configurable for now, see future development). Bulk size is designed this way, because events are processed by priority - event with ''HIGH'' priority should not wait too long for another bulk is begin to process. Remove duplicates should be redesigned from scratch - remove duplicates through whole queue. | Older duplicate events are removed - the newest event is used. Events are processed by priority in bulk, default bulk size can be [[..:..:application_configuration:dev:backend#entity_events|configured]] => duplicates are removed only in this bulk (not configurable for now, see future development). Bulk size is designed this way, because events are processed by priority - event with ''HIGH'' priority should not wait too long for another bulk is begin to process. Remove duplicates should be redesigned from scratch - remove duplicates through whole queue. |
| |
| |