Hi team, I found that Pinot sometimes shows that the table status is bad, and at the same time the corresponding segment is also bad (one replicas state is consuming, and the other is online), this bad state will be automatically recovered. So when querying, especially on-demand will the query get inconsistent results, or how will Broker choose which replicas to query when querying?

Are you seeing this in UI

This will be recovered soon. We hope to add some alarm items by monitoring the table state, but the bad state will always appear. I guess it is because the consumption speed of different replicas of the segment is slightly different. One replica has been submitted and the other is still consuming.

its a UI bug.. for a short second when the segment is transitioning from one state to another, it shows it as bad

This API ‘/tables/{tableName}/status’ response UNHEALTHY too.

{
  "ingestionStatus": {
    "ingestionState": "UNHEALTHY",
    "errorMessage": "Not all servers responded for segment: XXX, Missing servers : [XXX]"
  }
}

Can you see external view?

External view of this table is garbled while other tables are fine.

If you are using 0.8.0, can you check the debug endpoint? https://docs.pinot.apache.org/basics/getting-started/troubleshooting-pinot#is-there-any-debug-information-available-in-pinot