This message was deleted.
# troubleshootings
Slackbot
10/19/2022, 9:19 PMThis message was deleted.
j
Julian Reyes
10/19/2022, 9:26 PMAlso, running
kubectl logs druid-test-historical-9 --previousa
Adam Peck
10/19/2022, 10:38 PMWhat does
kubectl describe pod ...j
Julian Reyes
10/20/2022, 10:28 AMDont think it’s getting OOMKilled, running your command in events:
Copy code
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning BackOff 14m (x326 over 118m) kubelet Back-off restarting failed container
Warning Unhealthy 9m18s (x102 over 128m) kubelet Liveness probe failed: Get "<http://10.3.134.21:8083/status/health>": dial tcp 10.3.134.21:8083: connect: connection refused
Normal Pulled 4m9s (x35 over 129m) kubelet Container image "apache/druid:24.0.0" already present on machineJulian Reyes
10/20/2022, 10:29 AMit just never ends loading all segments and it exists but no error or relevant info that tell me what the problem was
Julian Reyes
10/20/2022, 10:30 AMI have 12 historical in total, 10 of them are running properly, 1 of them has not been created yet and the other is in this weird state where it exists
Julian Reyes
10/20/2022, 11:17 AMwell it looks like it ended up running after so many restarts attempts
a
Adheip Singh
10/20/2022, 4:49 PMyou lll need to increase your probe time
Adheip Singh
10/20/2022, 4:50 PMk8s will restart the pod if does not go 1/1 by a certain threshold.
j
Julian Reyes
10/20/2022, 6:06 PMCan you elaborate more on that?