Skip to content
Snippets Groups Projects
  • Mark Michelson's avatar
    c0a7df10
    Taskprocessors: Increase high-water mark · c0a7df10
    Mark Michelson authored
    In practical tests, we have seen certain taskprocessors, specifically
    Stasis subscription taskprocessors, cross the recently-added high-water
    mark and emit a warning. This high-water mark warning is only intended
    to be emitted when things have tanked on the system and things are
    heading south quickly. In the practical tests, the Stasis taskprocessors
    sometimes had a max depth of 180 tasks in them, and Asterisk wasn't in
    any danger at all.
    
    As such, this ups the high-water mark to 500 tasks instead. It also
    redefines the SIP threadpool request denial number to be a multiple of
    the taskprocessor high-water mark.
    
    Change-Id: Ic8d3e9497452fecd768ac427bb6f58aa616eebce
    c0a7df10
    History
    Taskprocessors: Increase high-water mark
    Mark Michelson authored
    In practical tests, we have seen certain taskprocessors, specifically
    Stasis subscription taskprocessors, cross the recently-added high-water
    mark and emit a warning. This high-water mark warning is only intended
    to be emitted when things have tanked on the system and things are
    heading south quickly. In the practical tests, the Stasis taskprocessors
    sometimes had a max depth of 180 tasks in them, and Asterisk wasn't in
    any danger at all.
    
    As such, this ups the high-water mark to 500 tasks instead. It also
    redefines the SIP threadpool request denial number to be a multiple of
    the taskprocessor high-water mark.
    
    Change-Id: Ic8d3e9497452fecd768ac427bb6f58aa616eebce