pradeep-jangid commented on issue #16226:
URL: https://github.com/apache/pinot/issues/16226#issuecomment-3032669094
@Jackie-Jiang We've figured out the root cause where Pinot (in Low-Level
Kafka consumer mode) has recorded a Kafka offset that is ahead of Kafka's
latest offset for a partition. This causes Pinot to silently skip the partition
entirely.
For Kafka partition 9:
Pinot’s currentOffsetsMap: 36976355
Kafka’s actual latest offset: 17553131
recordsLagMap: -19423224 (negative)
Pinot server logs show that consumption is active (CONSUMING), but no new
rows from that partition appear in Pinot queries.
What We Validated
No pinot_server_realtimeRowsDropped_Count reported
Segment is in IN_PROGRESS
No errors or warnings in Pinot logs
/consumingSegmentsInfo API output for the partition -
```
"TableName__9__518__20250702T1319Z": [
{
"serverName": "Server_prod-pinot-server-1",
"consumerState": "CONSUMING",
"lastConsumedTimestamp": 1751482248595,
"partitionToOffsetMap": {
"9": "38145385"
},
"partitionOffsetInfo": {
"currentOffsetsMap": {
"9": "38145385"
},
"latestUpstreamOffsetMap": {
"9": "38145385"
},
"recordsLagMap": {
"9": "0"
},
"availabilityLagMsMap": {
"9": "2"
}
}
}
]
```
But We still don’t know how Pinot’s offset went ahead of Kafka's for single
partition.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
