jpappa200 opened a new issue, #7191:
URL: https://github.com/apache/trafficcontrol/issues/7191

   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! 
Instead, contact
   the Apache Traffic Control Security Team at 
[email protected] and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack 
(https://s.apache.org/tc-slack-request)
   or the Traffic Control Users mailing list (send an email to 
[email protected] to subscribe).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
       * https://github.com/apache/trafficcontrol/issues
       * https://github.com/apache/trafficcontrol/pulls
   -->
   
   <!-- Do not submit security vulnerabilities or support requests here - see 
above -->
   ## This Improvement request (usability, performance, tech debt, etc.) 
affects these Traffic Control components:
   <!-- delete all those that don't apply -->
   
   - Traffic Control Health Client (tc-health-client)
   
   
   ## Current behavior:
   <!-- Describe how the current features are insufficient. -->
   v3 API will be deprecated soon and needs to updated to v4. The last redesign 
requires a SIGHUP to reload the config file. we need to add a reload option to 
the systemd config. 
   
   ## New behavior:
   <!-- Describe how this change would improve Traffic Control -->
   The servers endpoint in the v4 API is more efficient and reduces the amount 
of failures when contacting the TO API and also eliminates the need for longer 
timeout settings.
   The last redesign requires a SIGHUP to reload the config file when changes 
are made. adding a reload option to systemd makes it easier for automation such 
as ansible to reload the configs. 
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to