<@UGRJA9TEH> in Pinot if two tables are consuming ...
# troubleshooting
r
@Xiang Fu in Pinot if two tables are consuming from one topic with 1 partition, does the data in both tables can cause any issue? what if we use two different consumer group Ids for both will it solve the issue. Also how to find to the consumption rate in pinot if it is low how can we increase it?
x
pinot internally handles the consuming offsets based on kafka partitions
you can create as many tables to consume from the same kafka topic.
How low do you see from the pinot consumption? Pinot uses 1 thread to consume from 1 kafka partition, so if you have high throughput topic, we suggest to have more kafka partitions
r
oh okay, I am seeing very less 900-1000 max messages consumed per second
partition is 1
x
ok, what’s the incoming write throughput to kafka?
usually for normal traffic we are running, Pinot could take as many as 10k msg/sec
r
our incomming kafka throughput is 1000 messages per 500ms
x
ok, so do you see any lag?
r
on kafka source topic I see a lag of ranging from 100-500 and on pinot I see incoming messages coming at a low rate of 160 messages at max
g
Rajat consider also the file size, i had the same issue when consuming 25kb(avg) kafka messages, decreasing the file size to around 4kb(avg) improved the consumption from 30msg/s to 3000msg/s - this is per partition data
x
Yeah, check the Kafka lag metrics from pinot. If that is flat then you are good. Upstream fluctuations may got smoothed afterwards at downstream