<p>version: 1.9.3-gke.0</p>
<p>Once every 30-45 mins I get a huge spike of nil events ~50k-1mm large groups having same timestamp</p>
<p>I'm running a pod inside the cluster the code is below. I've included some comments.</p>
<pre><code>hpaWatch, err := clientset.AutoscalingV1().HorizontalPodAutoscalers("").Watch(metav1.ListOptions{})
// .Watch(metav1.ListOptions{}) returns a watch.Interface which has a ResultChan() shown below (from source)
// Returns a chan which will receive all the events. If an error occurs
// or Stop() is called, this channel will be closed, in which case the
// watch should be completely cleaned up.
// ResultChan() <-chan Event
// The Event is a struct with an Object field below (from source)
// Object is:
// * If Type is Added or Modified: the new state of the object.
// * If Type is Deleted: the state of the object immediately before deletion.
// * If Type is Error: *api.Status is recommended; other types may make sense
// depending on context.
// Object runtime.Object
for {
select {
case event := <-hpaWatch.ResultChan():
if event.Type == "ADDED" || event.Type == "MODIFIED" {
go handleEventz(event)
} else {
log.WithFields(log.Fields{
"event": event,
}).Error("This event was not ADDED or MODIFIED")
}
}
}
</code></pre>
<p>then thousands to millions of these in the logs</p>
<pre><code>time="2018-04-19T03:32:04Z" level=error msg="This event was not ADDED or MODIFIED" event="{ <nil>}"
</code></pre>
<hr/>**评论：**<br/><br/>BadlyCamouflagedKiwi: <pre><p>Could the channel have been closed? That would cause all reads to return immediately with a nil event.</p>
<p>Ranging over the channel itself in the for loop would help with that (and it's a bit less code too).</p></pre>arkrish: <pre><p>This is a well known issue when the channel is closed after a time out. A similar issue is on node watch events: <a href="https://github.com/kubernetes/client-go/issues/334#issuecomment-378752777" rel="nofollow">https://github.com/kubernetes/client-go/issues/334#issuecomment-378752777</a></p>
<p>A workaround/coding pattern is also described there. </p></pre>
