#vserver max-watches-set-per-tree exceeded

1 messages · Page 1 of 1 (latest)

trail oracle
#

I am getting a number of these events in my log:

Nblade.cifsMaxWatchesPerTree: Received too many Change Notify requests on one tree:

Docs say this is controlled by:

vserver cifs options show -fields max-watches-set-per-tree

How can you figure out what value it should be set to? Or should I just ignore the errors?

paper rune
#

It's a tradeoff. You can set it higher but at some point it will consume quite a bit of memory and resources on the controller. I wouldn't increase it to more than 2-3 times the initial value. You can also ignore it, it should not cause any issues (your clients will just fall back to polling)