Bug 1471957 - When performing a rolling deployment of a large container on Online us-east-1, some router instances don't include endpoints
Summary: When performing a rolling deployment of a large container on Online us-east-1...
Keywords:
Status: CLOSED DUPLICATE of bug 1471899
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Routing
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-17 19:16 UTC by Clayton Coleman
Modified: 2017-08-31 17:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-31 17:33:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Clayton Coleman 2017-07-17 19:16:32 UTC
We have a prometheus instance in us-east-1 that, when updated, takes 20minutes to 3hours for each router instance to start including it again.  The endpoints are in place for the service (the new pod IP is in endpoints), but only some of the routers show up.

Project openshift-devops-monitor route prometheus

Comment 1 Clayton Coleman 2017-07-17 19:17:06 UTC
Only some of the router instances return the app - the others return a 503 for a very long time.  This is 3.6.126/8

Comment 2 Ben Bennett 2017-07-28 19:17:47 UTC
Please see the comment at https://bugzilla.redhat.com/show_bug.cgi?id=1471899#c2 for a way to tune things to work around this problem for the short term.

Comment 3 Ben Bennett 2017-08-31 17:33:20 UTC

*** This bug has been marked as a duplicate of bug 1471899 ***


Note You need to log in before you can comment on or make changes to this bug.