Apache Pinot

Hello :wave:
I have 3 of my 4 servers stuck with this kind of message:
```Find unloaded segment: &lt;tableName&gt;__0__35__20220404T0749Z, table: &lt;tableName&gt;_REALTIME, expected: ONLINE, actual: CONSUMING
Sleeping 1 second waiting for all segments loaded for partial-upsert table: &lt;tableName&gt;_REALTIME```
Which endpoint should I use to try to sort this out? The `reload` one does not work, for the segment is still consuming and the `reset` always fails, for it can't stop a consuming segment for some reason.

Would it be okay to just delete this segment? Would the Controller know it needs to be consumed again?

deleting the consumig segment won’t help. it’ll get stuck.

<@UDT7GFEG6> ^ any idea about this error?

<@U02NCC1A717> Have you tried restarting the servers?

Not sure how you run into this scenario. Somehow the consuming segment is already committed, but the failed servers haven't started consumption yet

<@UDT7GFEG6> yes, this started happening after a restart.
And by restart I mean:
we are deploying on k8s through the helm chart and, after changing the resource config (bumping up RAM), the servers' pods were recreated

<@U02NCC1A717> Can you please check the ideal state and the external view of this segment? When server is restarted, the segment should directly go to ONLINE state instead of CONSUMING state

Not anymore... we removed everything and we have a fresh new deployment. Everything is working fine for now.

But what would happen if the segment didn't get committed before we restarted the servers? Would it still appear as `ONLINE`, even if not "complete"?

So, I'm having a similar problem again:
```Find ERROR segment: &lt;tableName&gt;__100__45__20220409T0856Z, table: &lt;tableName&gt;_REALTIME, expected: ONLINE                                                                                                                                                 
Sleeping 1 second waiting for all segments loaded for partial-upsert table: &lt;tableName&gt;_REALTIME```
When I try to reload the segment, I see this message in the logs:
```Reloading single segment: &lt;tableName&gt;__100__45__20220409T0856Z in table: &lt;tableName&gt;_REALTIME                                                                                                                                                           
Segment metadata is null. Skip reloading segment: &lt;tableName&gt;t__100__45__20220409T0856Z in table: &lt;tableName&gt;_REALTIME```