Re: Brokered route services only receiving traffic for routes mapped to started apps


Mike Youngstrom <youngm@...>
 

Here is another minor use case. My users are often confused that a stopped
app returns a 404 instead of a 503. So, we implement that functionality
for the user using an app mapped to wildcard routes that constantly asks
the CC for valid routes. This works for wildcard domains but not one off
domains.

It might be better if the router returned a 503. At least for routes bound
to apps. Not sure if this should extend to routes not bound to apps.

Mike

On Thu, Apr 28, 2016 at 1:32 PM, Shannon Coen <scoen(a)pivotal.io> wrote:

Hello Guillaume,

Thank you for sharing your thoughts on these use cases. I can see how
having
a route service field requests for an app, whether the app is up on not,
could be useful.

However, enabling this would significantly change how routes are registered
for apps on Cloud Foundry, and how the router handles the route lookup.
Routes are not currently enabled in the routing tier unless they are mapped
to an app, and only when the app is determined healthy.

You are proposing the router maintains routes which have no backends, and
instead of a failed lookup determining whether a 404 is returned, the
router
should figure out whether a route has any backends or a route service.

I'll chew on your use case and keep my ear out for additional use cases for
maintaining routes with no backends in the routing table.

Best,
Shannon



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/cf-dev-Brokered-route-services-only-receiving-traffic-for-routes-mapped-to-started-apps-tp4699p4742.html
Sent from the CF Dev mailing list archive at Nabble.com.

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.