Hi team, my table segments show bad status. Queries on this table return 305 error and segments are not available. I reset all segments and it doesn’t work. What am I gonna do in this case? Thanks.

You can try the following:

- Check debug api in swagger if it bubbles up some errors
- Check controller/server logs for any errors like OOMs
- Check if have enough resources assigned to your pinot components.

Thanks, Mayank.

Is there a way to recover from this state? Can we force a reset in consumption and re-consume that data?

Yes, but it will depend on what caused it. If under resourced, then adding more nodes. Do you know what caused the issue in your particular case?

In my case, I know it is not under resourced. We have 4 servers with 64gb of RAM. One server restarted for an unknown reason during the weekend and looks like a bunch of segments "were lost". Besides this result when querying, the servers started showing errors for segments, like on this thread. Reloading and resetting segments didn't work. And once those errors start to appear, the servers start to top CPU usage because all threads are sleeping

waiting for all segments loaded for partial-upsert table

I couldn't recover from this state, I had to nuke the table and re-start comsumption. I would like to just "re-consume" data for those segments, if that was possible

Ok I’ll need to understand the setup will ping