-
Type:
Task
-
Resolution: Done
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: backend
-
None
-
80
Context:
To isolate the ingestion API from normal user requests we should either assign it a dedicated threadpool if possible or serve it with a dedicated jetty on different ports (http/https).
AT:
- a high load of requests against the event ingestion API doesn't heavily impact the performance of the rest of the API
1.
|
Evaluate different options for isolating the ingestion API |
|
Done | Unassigned |
2.
|
Add QoS filter to limit the number of ingestion requests at any given time |
|
Done | Unassigned |
3.
|
Respond with correct error code when we can't serve ingestion API requests |
|
Done | Unassigned |
4.
|
Disable the event ingestion endpoints if disabled in configuration |
|
Done | Unassigned |