https://pinot.apache.org/ logo
#troubleshooting
Title
# troubleshooting
a

Ali Atıl

04/07/2022, 6:39 AM
Hello everyone, is it normal for pinot-server to flood this log? i have noticed this after upgrading to 0.10.0
[Consumer clientId=consumer-null-808, groupId=null] Seeking to offset 59190962 for partition mytopic-0
m

Mayank

04/07/2022, 9:34 PM
Seems like this is coming from the kafka consumer
a

Ali Atıl

04/08/2022, 5:58 AM
Do you think it is printed because something went wrong or it's completely normal to see this log flooding?
l

Luis Fernandez

07/27/2022, 2:28 PM
seeing this happen a lot in our cluster but i’m not sure if it’s a bad thing or not, anyone has any ideas?
it doesn’t let me see any other logs about the server lol
m

Mayank

07/27/2022, 5:24 PM
@Neha Pawar ^^
n

Neha Pawar

07/27/2022, 5:37 PM
yup coming from kafka consumer. it comes from seek(topic, offset) call we make to the KafkaConsumer, so we don’t really have control on it. I don’t know if there’s a way for us to edit our log4j.xml file to skip this log. As long as this log is not being followed by this message, it is harmless: https://github.com/apache/pinot/issues/8219
l

Luis Fernandez

07/27/2022, 6:05 PM
thank you @Neha Pawar 🙏
g

Gerrit van Doorn

07/29/2022, 5:38 PM
@Neha Pawar I’m seeing this behavior currently. My config is
Copy code
"streamConfigs": {
        .
        "stream.kafka.consumer.prop.auto.offset.reset": "largest"
      },
so why would it be seeking? Shouldn’t it start consuming from the latest offset?
n

Neha Pawar

07/29/2022, 5:40 PM
if all you’re seeing is
[Consumer clientId=consumer-null-808, groupId=null] Seeking to offset 59190962 for partition mytopic-0
, it’s fine. this simply gets printed everytime the kafka consumer created in pinot servers calls consumer.seek()