Jump to: navigation, search

GVP MCP:mpc:health-waittime

 
(6 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
|valid=mpc.health.waittime must be an integer no less than 0.
 
|valid=mpc.health.waittime must be an integer no less than 0.
 
|takeseffect=At start/restart
 
|takeseffect=At start/restart
|shortdesc=Specifies the wait time in milliseconds for Health Thread to check the health of media threads periodically. It is reasonable to set health.waittime smaller than health.maxprocessingtime. Default value is 0, meaning MCP will not perform health check. Note: do not enable health check unless it is really necessary, e.g. MCP has to restart in order to recover from a stuck situation.
+
|shortdesc=
 +
Specifies the wait time in milliseconds for Health Thread to check the health of media threads periodically. It is reasonable to set health.waittime smaller than health.maxprocessingtime.
 +
Default value is 0, meaning MCP will not perform health check. Note: do not enable health check unless it is really necessary, e.g. MCP has to restart in order to recover from a stuck situation.
 +
 
 
}}
 
}}
 
{{DraftOption}}
 
{{DraftOption}}

Latest revision as of 15:58, June 29, 2020



View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

health.waittime

Default Value: 0
Valid Values: mpc.health.waittime must be an integer no less than 0.
Changes Take Effect: At start/restart


Specifies the wait time in milliseconds for Health Thread to check the health of media threads periodically. It is reasonable to set health.waittime smaller than health.maxprocessingtime. Default value is 0, meaning MCP will not perform health check. Note: do not enable health check unless it is really necessary, e.g. MCP has to restart in order to recover from a stuck situation.

Draft Option

No draft option

This page was last edited on June 29, 2020, at 15:58.
Comments or questions about this documentation? Contact us for support!