You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2020/11/17 17:32:10 UTC

[GitHub] [trafficcontrol] rob05c commented on issue #2649: Traffic Ops should ping the database on startup

rob05c commented on issue #2649:
URL: https://github.com/apache/trafficcontrol/issues/2649#issuecomment-729084107


   Hm, I think I might've changed my mind on this.
   
   It's really handy to have TO _not_ require the DB to start, and only when you actually make a request.
   
   It makes debugging and developing much easier, not having to start the DB first and guarantee it's running.
   
   But I think it also makes the TO service more resilient. It means you don't have a required startup order, TO itself can run and function independently of the database, and the DB can not exist on startup, go down and back up at any time, etc. And it's only an issue if the DB is unavailable when a request is actually made. And only affects that particular request, not the TO Service itself.
   
   I think all that is valuable, and makes TO more robust and resilient.
   
   But a warning/error log message on startup wouldn't be bad.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org