memory usage grows up daily in unexpected way

No problem... what's your case number? I tried looking but didn't find it.

 

 

I don't see any glaring issues after a cursory look over the rules.

 

 

You can measure the memory usage for the bug in CR70058 by running:

 

 

tmctl umem | grep -i alloc

 

 

Check the values for umem_alloc_8, umem_alloc_16, and umem_alloc_2504 to see if they grow. To force the failure, you could disable the nodes in the pool--but to see if this is the specific bug you're encountering, you could just append the output to a file and see if the counters increment over the course of a day or two. If they increase as the rule is hit and connections fail, then you've encountered this bug. If not, then I'd suggest you continue working with support to see what is causing the memory leak.

 

 

Aaron