You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have observed that dockergen calls '/events' huge number of times when the docker daemon is not fully initialized. As a result of this docker 1.9.1 consumes a lot of memory more than 4GB (when it should only be consuming 40MB).
Sample logs:
Jan 03 22:17:56 host docker[966]: time="2018-01-03T22:17:56.527161876+11:00" level=info msg="GET /events"
Jan 03 22:17:56 host docker[966]: time="2018-01-03T22:17:56.527770917+11:00" level=info msg="GET /events"
Jan 03 22:17:56 host docker[966]: time="2018-01-03T22:17:56.529030241+11:00" level=info msg="GET /events"
Jan 03 22:17:56 host docker[966]: time="2018-01-03T22:17:56.529666130+11:00" level=info msg="GET /events"
Number of times called per second:
Table shows columns timestamp and number of times '/events' called'.
We have observed that dockergen calls '/events' huge number of times when the docker daemon is not fully initialized. As a result of this docker 1.9.1 consumes a lot of memory more than 4GB (when it should only be consuming 40MB).
Sample logs:
Number of times called per second:
Table shows columns timestamp and number of times '/events' called'.
The text was updated successfully, but these errors were encountered: