This message was deleted.
# troubleshooting
s
This message was deleted.
c
I am running 0.23 with some local bug fixes to the k8s extension. We also automatically cycle out the coordinator pods every 3 hours to ensure leadership is fresh. There is definitely another bug I have to track down (time allowing) that stabilizes it so that I can submit the fix upstream.
Cycling the pods works around the stability issue.
👀 1
The other fixes I am using are pretty small.
One thing I noticed is that the logs quickly fill up with errors, but the error is actually more like a debug statement using error level, so it looks like things are very broken, but in fact everything is fine.
I'm going to discuss a lot of this in my druid summit talk
r
as far as I can remeber, it was a null point exception when downloading some metadata from the k8s
d
I suffered the same NPE like @Renato Santos last time I tried it. But to be honest, I didn’t try very hard because it looked like it’s not ready.
c
I am pretty sure I fixed that NPE in my internal fork. As soon as I am happy with the stability I'll PR it upstream.
Following that I'll upgrade to the lates kubernetes client also.
❤️ 1
g
🙌 looking forward to it!!