ben.carrasco/jambonz-infrastructure
1
0
Fork 0
mirror of https://github.com/jambonz/jambonz-infrastructure.git synced 2026-01-25 02:08:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

minor

Browse Source
This commit is contained in:
Dave Horton
2020-04-21 10:21:25 -04:00
parent 8dbd6ccd9f
commit 881ffe30ec
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -20,13 +20,13 @@ The feature servers make use of AWS SNS lifecycle notifications to scale-in grac
#### temporarily taking a feature server out of service
If you want to temporarily take a feature server out of rotation (not receiving any calls from the SBCs), there is a two step process to do so:
1. Using the AWS console or cli, select the instance of the autoscale group and put it into Standby state.
1. Using the AWS console or cli, select the instance within the autoscale group and put it into Standby state.
2. Once the instance is in standby state, ssh into the instance and again send a SIGHUP signal to the node.js process running the feature server application. This will cause the feature server to send an OPTIONS request to the SBC indicating that it is out of service.
At that point, you need to wait for any calls in progress on the feature to dry up. Once they do, you can then perform your maintenance or troubleshooting as needed.
To bring the feature back into service once the maintenance is complete, do the following:
1. Using the AWS console or cli, select the instance of the autoscale group and put it back into the InService state.
1. Using the AWS console or cli, select the instance within the autoscale group and put it back into the InService state.
2. Once the instance is in the InService state, ssh into the instance and send a SIGHUP signal to the node.js process running the feature server application. This will cause the feature server to send an OPTIONS request to the SBC indicating that it is back in service.