kubernetes - Kubelet fails to update node status -


on latest rhel atomic host (kubernetes 1.2) regularly seeing following entries in kubelet logs:

kubelet.go:2761] error updating node status, retry: nodes "x.y.z" cannot updated: object has been modified; please apply changes latest version , try again

this causes node temporary go notready. during these notready periods, pods on node show ready, looks kubernetes stops routing traffic them, causing problem.

in go sources can see during heartbeat of kubelet fetch latest status, overwrites own status, , sends put apiserver.

this see in logs:

jul 15 12:42:45 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:42:45.086322 3736 round_trippers.go:264] https://lxa160g.srv.pl.ing.net:6443/api/v1/nodes/lxa160j.srv.pl.ing.net jul 15 12:42:45 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:42:45.091579 3736 round_trippers.go:289] response status: 200 ok in 5 milliseconds jul 15 12:42:45 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:42:45.373091 3736 round_trippers.go:264] put https://lxa160g.srv.pl.ing.net:6443/api/v1/nodes/lxa160j.srv.pl.ing.net/status jul 15 12:42:45 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:42:45.409752 3736 round_trippers.go:289] response status: 200 ok in 36 milliseconds jul 15 12:42:55 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:42:55.411267 3736 round_trippers.go:264] https://lxa160g.srv.pl.ing.net:6443/api/v1/nodes/lxa160j.srv.pl.ing.net jul 15 12:42:55 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:42:55.431056 3736 round_trippers.go:289] response status: 200 ok in 19 milliseconds jul 15 12:43:38 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:43:38.020203 3736 round_trippers.go:264] put https://lxa160g.srv.pl.ing.net:6443/api/v1/nodes/lxa160j.srv.pl.ing.net/status jul 15 12:43:38 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:43:38.029575 3736 round_trippers.go:289] response status: 409 conflict in 9 milliseconds jul 15 12:43:38 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:43:38.029772 3736 round_trippers.go:264] https://lxa160g.srv.pl.ing.net:6443/api/v1/nodes/lxa160j.srv.pl.ing.net jul 15 12:43:38 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:43:38.034980 3736 round_trippers.go:289] response status: 200 ok in 5 milliseconds jul 15 12:43:38 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:43:38.298752 3736 round_trippers.go:264] put https://lxa160g.srv.pl.ing.net:6443/api/v1/nodes/lxa160j.srv.pl.ing.net/status jul 15 12:43:38 lxa160j.srv.pl.ing.net kubelet[3736]: i0715 12:43:38.320192 3736 round_trippers.go:289] response status: 200 ok in 21 milliseconds

so takes long time fire put after successful get. why?

thanks


Comments

Popular posts from this blog

java - Static nested class instance -

c# - Bluetooth LE CanUpdate Characteristic property -

JavaScript - Replace variable from string in all occurrences -