We are preparing to do a SLL certificate rotation for our octopus server, and exclusively use poling tentacles. (Expiring certificates and polling tentacles are hard requirements from our customers)
While preparing for the rotation for the production server we have been attempting to test rotating on our Development server. In order to maintain constant tentacle connections we are attempting to add the new SSL thumbprint trust to existing tentacles, and otherwise use the same connection properties. This approach is working for keeping constant connectivity, however it has uncovered another issue.
As we increase the number of tentacles that are attempting to connect with the wrong thumbprint the Octopus server responsiveness is reduced. One of our development servers has approximated 300 tentacles and when most of them are updated to have the second thumbprint the Server UI is intermittently unusable. The active ‘health’ pings from the UI will report as taking up to a minute and a half. There is no option for configuring and extending the retry period for the polling Halibut connections, and our Production server has approximately 4000 tentacles. I am afraid it will become unusable entirely with that many tentacle connections bogging down the Server.
If there is any additional information I can provide please let me know, Thanks!