Open dolshevsk opened 9 months ago
I am also having this issue. It consistently produces INFO logs that are notifying me of a < 1s drift with no other consequences that I can tell. Have you attempted any workarounds?
I agree, it is really a nuisance, let me see what I can do to give us the option to tell the application that drift is inevitable and that we don't care.
Checklist
master
branch of Mode.Steps to reproduce
Hey there, I'm building quite intense streaming application and my logs just spammed with
Timer _thread_keepalive-AIOKafkaConsumerThread woke up too late
when theabs(drift)
value between 0.3-0.5 what from my perspective isn't a big problem and doesn't need too much reaction.Expected behavior
It would be great if
max_drift
could be configured somehow so it can be set to1.0
when the lag is inappropriate, or produce a log only whenself.drifting
threshold is reached.Actual behavior
Currently there is no option to configure either the
max_drift
orself.drifting
thresholds.Full traceback
Versions