Comment 7 for bug 1966176

Revision history for this message
Maurice Escher (maurice-escher) wrote :

Turning trace flags on in production is not an option sadly.

We see this error like in 1 of 200k share creations. My assumption is that it is related to high cpu load on the nodes. The last occurrence is too far in the past to make useful correlations, waiting for it to happen again...

Can you nevertheless try to improve the delete use case? When the share instance is going to be removed anyway there is no need to update export policies one by one, just get rid of all of them and don't care for errors, no?