Grid Advanced Settings
The following Advanced Settings are available for grids via the Summary and Deploy/Tear Down page:
- Allocation block size
This setting will specify the server block size (e.g. the number of server instances to try at once).
For example, the user wants 500 Test Servers. Typically, if the user wants a large number of Test Servers, we can't ask for them all at once. If CloudTest asks for 500 Test Server instances all at once, the request will probably be rejected ("insufficient capacity", etc.). But, if CloudTest asks for them in blocks of 25, then some will succeed and some will fail. CloudTest can take just the failed ones and re-try them in a different zone.
- Allocation failure retry count
For the total allocation request, specify a maximum number of times to retry.
The re-try algorithm described above in the Block Size description includes two types of errors (in the case of Amazon EC2):
- Failures that are on the Amazon side, e.g. "Insufficient capacity". For these errors, we immediately fail over to a different zone.
- Failures that are probably due to networking issues (e.g. network connection reset). For these errors, we will re-try in the same zone, but only a certain number of times.
- Allocation failure retry delay
For the set of allocation requests, specify a number in seconds between retries.
For same-zone re-tries, delay this number of seconds first.
- Use Extra Large Instances If Necessary
This default, if checked, provides the ability to Fail Over to XL Instances. This setting permits XL instances to be called upon if allocation to L instances is insufficient.
- Automatically Monitor Grid
Start the default monitors for each server. See Default Monitoring
- Automatically Delete Monitors
When checked, automatically delete default monitors when the grid is shut down. To review the monitoring data later on, turn off this setting. This is usually left on, because the monitoring data is usually used just to "keep an eye on things" during the test.
- Check Servers automatically
Initiate "check servers" as part of this server deployment.
This setting should be left on. If it's checked, then after all servers have reached the "Running" state, we do a "health check" of the CloudTest services (e.g. Test Server) on each server.
- Check Server retry count
Specify the number of times to retry the server allocation.
Usually, the first "health check" of a server will fail—just because the machine has booted, it doesn't mean that JBoss has finished starting, etc. So, CloudTest will re-try, if necessary. The max number of retries is this setting.
- Check Server retry delay
Specify the time in seconds to delay between retries.
To deploy a server based on an Amazon EC2 High Performance Computing class, use the Grid Manager, Server Instances page, Server Class drop-down ( whenever Show advanced settings is checked).
- Click Deploy Instances when ready. A spinner will appear while the default monitor is starting and stops when that phase is complete.
Clicking Proceed with X of X while it's active displays these subsequent options:
- Terminate Pending – Choose this option to terminate the remainder of the server allocation tasks. When you do so, the Proceed window disappears and the grid is ready to be used with the number of servers indicated by the Proceed button (i.e. 4 of 11, etc.)
- Keep Allocating Pending – Choose this option to resume the server allocation for the remaining servers.
If Proceed was clicked, and then Terminate Pending, the Proceed window will go away. Then the following behavior will occur:
- Any already-allocated servers will “proceed” through the usual grid process, including server-health checking.
- Any servers that were still pending will be terminated.
What you should see
The Grid Ready icon will display only once (i) and (2) are complete.
The Stopped icon will display whenever all of the requested servers failed to be allocated or if the Stop Deploying button is clicked.
When grid use is complete, click the Tear Down Instances button. When you do so, the grid indicates progress in the status area of the Journal tab.