数据流流媒体作业的消耗并未结束

时间:2017-01-03 13:11:51

标签: google-cloud-dataflow

我执行了" drain"使用此命令进行流媒体作业

  

gcloud alpha dataflow jobs --project = xxxxxx drain

但三天后它没有结束! 这是此流媒体工作的日志。

21:14:36.000
http: TLS handshake error from 172.17.0.2:40277: EOF
21:14:36.000
http: TLS handshake error from 172.17.0.2:36255: EOF
21:14:36.000
Kubelet is healthy?: true
21:14:42.000
http: TLS handshake error from 172.17.0.2:55731: EOF
21:14:42.000
Kubelet is healthy?: true
21:14:47.000
http: TLS handshake error from 172.17.0.2:60835: EOF
21:14:47.000
Kubelet is healthy?: true
21:14:48.208
Memory is used/total/max = 71/207/1801 MB, GC last/max = 0.00/0.00 %, #pushbacks=0, gc thrashing=false
21:14:48.403
Memory is used/total/max = 454/852/1801 MB, GC last/max = 0.00/27.00 %, #pushbacks=0, gc thrashing=false
21:14:49.020
Memory is used/total/max = 38/117/1801 MB, GC last/max = 0.00/0.00 %, #pushbacks=0, gc thrashing=false
21:14:49.245
Memory is used/total/max = 457/1092/1801 MB, GC last/max = 0.00/21.00 %, #pushbacks=0, gc thrashing=false
21:15:06.000
Kubelet is healthy?: true
21:15:06.000
http: TLS handshake error from 172.17.0.2:36348: EOF
21:15:06.000
Kubelet is healthy?: true
21:15:06.000

我取消了这份工作。 但是我担心数据丢失。

我想使用" drain"而不是"取消" 我怎样才能耗尽流媒体工作?

1 个答案:

答案 0 :(得分:1)

总结评论主题:这是托管数据流服务中的一个缺陷,后来由服务版本修复。根本问题是优先级倒置导致消息处理死锁。