开发者社区> 问答> 正文

在阿里云VPC环境下,部署了k8sV1.11.1高可用集群,kubelet一直有报一个错误

Oct 18 10:03:20 worker001 kubelet[18956]: E1018 10:03:20.625638 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91373; INTERNAL_ERROR
Oct 18 10:04:03 worker001 kubelet[18956]: E1018 10:04:03.711397 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91511; INTERNAL_ERROR
Oct 18 10:04:38 worker001 kubelet[18956]: E1018 10:04:38.792179 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91529; INTERNAL_ERROR
Oct 18 10:05:03 worker001 kubelet[18956]: E1018 10:05:03.812098 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91643; INTERNAL_ERROR
Oct 18 10:05:48 worker001 kubelet[18956]: E1018 10:05:48.638481 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91681; INTERNAL_ERROR
Oct 18 10:06:03 worker001 kubelet[18956]: E1018 10:06:03.896857 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91781; INTERNAL_ERROR
Oct 18 10:06:53 worker001 kubelet[18956]: E1018 10:06:53.674940 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91819; INTERNAL_ERROR
Oct 18 10:07:03 worker001 kubelet[18956]: E1018 10:07:03.975904 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91853; INTERNAL_ERROR
Oct 18 10:07:54 worker001 kubelet[18956]: E1018 10:07:54.042442 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91907; INTERNAL_ERROR
Oct 18 10:08:04 worker001 kubelet[18956]: E1018 10:08:04.055452 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91933; INTERNAL_ERROR
Oct 18 10:08:54 worker001 kubelet[18956]: E1018 10:08:54.129991 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 91995; INTERNAL_ERROR
Oct 18 10:09:04 worker001 kubelet[18956]: E1018 10:09:04.144145 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 92005; INTERNAL_ERROR
Oct 18 10:09:54 worker001 kubelet[18956]: E1018 10:09:54.218016 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 92071; INTERNAL_ERROR
Oct 18 10:10:04 worker001 kubelet[18956]: E1018 10:10:04.232644 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 92085; INTERNAL_ERROR
Oct 18 10:10:54 worker001 kubelet[18956]: E1018 10:10:54.302705 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 92147; INTERNAL_ERROR
Oct 18 10:11:04 worker001 kubelet[18956]: E1018 10:11:04.316685 18956 streamwatcher.go:109] Unable to decode an event from the watch stream: stream error: stream ID 92161; INTERNAL_ERROR

目前集群运行正常,但是通过kubectl get nodes -w会发现偶尔节点会NotReady状态,大约40s左右偶尔一下,大部分时间都是正常running状态。这个导致的结果是我通过外部访问集群的服务,偶尔出现:
java.net.ConnectException: 拒绝连接 (Connection refused)
不知道是我的服务部署问题,还是集群本身的问题。

展开
收起
ang 2018-10-18 10:17:28 6000 0
2 条回答
写回答
取消 提交回答
  • ang

    NotReady的问题已经找到,是因为配置了controller-manager的node-monitor-grace-period: 10s 和 pod-eviction-timeout: 10s导致controller获取不到node的状态,影响了node上的服务,只需要改成默认值即可,现在集群中的服务正常了。
    但是在kube-proxy中还是有很多下面的错误,不知道什么原因:
    Unable to decode an event from the watch stream: stream error: stream ID 92071; INTERNAL_ERROR

    2019-07-17 23:09:04
    赞同 1 展开评论 打赏
  • 一直在编程方面学习

    是不是集群配置的原因

    2019-07-17 23:09:04
    赞同 1 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
Deep Dive:云上VPC分层安全架构设计 立即下载
经典网络迁移VPC最佳实践 立即下载
AWS 数据中心与 VPC 揭秘 立即下载