You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by "Mclain, Warren" <wa...@optum.com> on 2018/03/19 18:55:03 UTC

HTTPConnectionPool(host='leader.mesos', port=5050): Read timed out.

We have started seeing the following errors and corresponding slowdown in our 2 primary mesos clusters. Both are running DCOS 1.10.5 /Mesos 1.4.2.

Mar 19 18:36:26 gunicorn[31061]: [WARNING:2018-03-19 18:36:26,619] Could not fetch state: HTTPConnectionPool(host='leader.mesos', port=5050): Read timed out. (read timeout=1.8)
Mar 19 18:36:56 gunicorn[31061]: [WARNING:2018-03-19 18:36:56,457] Could not fetch state: HTTPConnectionPool(host='leader.mesos', port=5050): Read timed out. (read timeout=1.8)
Mar 19 18:37:27 gunicorn[31061]: [WARNING:2018-03-19 18:37:27,555] Could not fetch state: HTTPConnectionPool(host='leader.mesos', port=5050): Read timed out. (read timeout=1.8)

This appears to be a limit of some type but so far we can't find anything. Looking to see if anyone has run across this.

___________________________________
Warren McLain
Enterprise Engineering Services
IEI Foundation Engineering - Compute, Optum Technology
 warren_mclain@optum.com Office: 763-744-3107


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.