This message was deleted.
# troubleshootings
Slackbot
11/13/2022, 11:15 PMThis message was deleted.
d
Didip Kerabat
11/14/2022, 12:52 AMthis sounds like you historical capacity is too small
m
Max Gorinevsky
11/14/2022, 12:03 PMYes - this sounds like some sort of resource contention. It's hard to say without looking at the cluster what the resource is, but task heap or task slots are likely culprits.
g
Gian Merlino
11/15/2022, 6:28 AMyou won't have parse exceptions due to resource constraints — that's likely really some issue in your data or your ingestion command
Gian Merlino
11/15/2022, 6:29 AMyou can have rows appear to drop due to resource constraints though; like didip said, this can happen if historicals are 'full'. you can see this in the Services tab of the web console. if you are in this situation, the apparently-dropped rows will come back if resources are increased
j
JW Sun
11/20/2022, 12:25 AMhello , this definitely happened, if I reduce the number of workers on the middle manager or manually ingest the individual task one by one from console, I don’t have any issues. I will try to reproduce it and share the logs.
g
Gian Merlino
11/21/2022, 10:12 AMok - that will be helpful, appreciate it!