OpenShift 3 API Observed a panic killing connection/stream because serving request timed out.

Solution Verified - Updated -

Issue

  • Observed a panic: &errors.errorString{s:"killing connection/stream because serving request timed out and response had been started"} (killing connection/stream because serving request timed out and response had been started)
  • Seeing degraded cluster performance when making API calls and API logs show Panics with goroutine dumps.
  • apiserver panic'd on GET /api/v1/pods?limit=500&resourceVersion=0: killing connection/stream because serving request timed out and response had been started

Environment

OpenShift Container Platform

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content