NODE CONTROLLER CONFIGURATION SECTION
To enable HTTP node monitoring, modify the following lines in the NODE CONTROLLER CONFIGURATION SECTION - MILLISECONDS
section:
instancecontroller.checkCorruptedNodes=false
instancecontroller.corruptedNodeCheckInterval=300000
instancecontroller.corruptedNodesEndPoint=live
instancecontroller.httptimeout=30000
- Change
instancecontroller.checkCorruptedNodes=false
toinstancecontroller.checkCorruptedNodes=true
- The default check interval (
instancecontroller.corruptedNodeCheckInterval
) is set to 300,000 milliseconds (5 minutes). You can make this more or less aggressive, keeping in mind that the more nodes you have active, the more load this will place on your stream manager. instancecontroller.corruptedNodesEndPoint
is the webapp to target checking. The default webapp is thelive
webapp, but if you have a custom webapp and/or are not using the defaultlive
webapp, you can change this to target a different webappinstancecontroller.httptimeout
is set to 30,000 (30 seconds) by default. This means that when it is checked, the node has 30 seconds to respond to the http request. If the stream manager doesn’t get any response, or gets an error response, then the node will be terminated and replaced. As with thecheckInterval
, you can make this more or less aggressive as you wish.