This message was deleted.
# troubleshooting
s
This message was deleted.
j
Literally was dealing with this all day yesterday. I was getting this inside the K8s jobs that were launching as a replacement for middleManager. Is that where you were seeing it too? CC @churro
Here is what I was told by the
MM-less
feature developer (paraphrasing):
Copy code
oh yeah ignore those 
so it thinks its an overlord but its not, service discovery doesn't need to happen in the peon task but since its another extension I havent been able to get to it yet
...
so service discovery only needs to happen for long lived processes, the peon task…because it inherits from the overlord has the service discovery as well but its useless
My issue is that tasks, even
{"type":"noop"}
are succeeding but reporting FAILED in the UI and I never ended up being able to figure out why
l
I have exactly that problem. It looks like the task is even putting data on my s3 deepstore, but never reporting successful in Druid I did find out that the role needed "pods/log" as well to display logs in the UI, if anybody else has come across that one.
j
@Lasse Mammen yes that is identical to my setup/issue. I get logs in the S3 bucket as well and thats where I see the above errors which are supposedly benign. I had the setup working previously but when I started testing some changes to the helm chart I ended up in that state. I went all the way to giving full cluster admin permissions to the role and it didn't help
c
we are using mm-less druid in production. I did push up a few fixes for this, one has been merged the rest are not really being looked at by anyone else. I can honestly just push up one large changeset that fixes a lot of issues next week and you guys can fork it if you want to use the feature.
I have a few more locally, like upgrading clients, working better with druid montiors etc…
i am having a hard time getting anyone in the druid community to look at them and i don’t want to keep rebasing, so ill just push up a big patch and hopefully someone in the community will take interest
l
Thanks @churro, I actually tried a custom built with this one https://github.com/apache/druid/pull/13668 which didn't help sadly
c
so what is weird, is that the peon task is not reporting back to the overlord correctly right? Let me look into that more today, I haven’t had much free time to work on druid this week.
l
Happy to try any other patches on my cloud
y
I wanted to go with a custom build too. At this point, not sure if going back to ZK isn't the best approach
c
For our deployments this all seems to work….
we run zk-less + mm-less in production here, but our build is pretty forked, ill push up our changes next week
l
What k8s version are you running it on? I'm on 1.25
c
in one big PR so at least people can use it if they want
let me see
j
I'm 1.25 too
c
we have all different versions of k8s, we run a lot of druid clusters
1.23 is the highest version we are running on
somewhere between 1.16 and 1.23 is what we are running druid on k8s
l
I was initially suspecting role permissions because I discovered it needed "pods/log" to display logs in Druid, but I'm not seeing any exceptions thrown so I guess that's not it
y
This one seems to be merged: https://github.com/apache/druid/pull/13668
As of 2 weeks ago
c
yeah thats it, there are a few more
i upgraded the client too, haven’t pushed that patch fully, just got it to work on our clusters yesterday….the k8s client was pretty old
but for the task success part, when the task completes, it calls a UpdateStatusAction which makes a call back to the overlord to tell it, hey I am done and i finished successfully. Then the overlord records in the db and should have the correct state. I think something might be going on there.
l
if that fails would it not throw a clear exception tho? My peon logs are clean
c
yeah they are clean but the call is not being made for some reason successfully
so that should call back to the overlord
which then calls this
So the TaskRunnerUtils should get called, to update the status….i mean it sucks, but you could put a debug log there to show its called??? with the status
ill push up what i have on my local 25.x branch in one big PR for you guys, today / early next week. But we are running it here (in prod) and everything is working fine. Ours is pretty forked though. So ill get you guys exactly what we have here. I just don’t want to keep making individual PRs and have them rot, so I haven’t been pushing my changes upstream.
l
I could try that sure. Will take a bit to verify that
y
Thank you... I will try it too
l
I'm just wondering what would happen if it's not correctly configured as an encapsulated task? Could that be it? Then first block you referenced wouldn't execute
y
I'm at a Beta stage now with my prod, so I can try things.
c
okay i think i might see the issue
okay so like i said above
d
I would love to see that pr. I was thinking of making a few changes myself.
s
Hey @churro can you share the pr with this fix ?