Disable the CalcFieldsQueue invalidation on historical data load

#1

It seems that the AsyncProcessingDisabled TenantConfig flag is not sufficient to disable the invalidation of the CalcFieldsQueue. When inserting new data (historical upload) we still get new entries in the queues.
Is there an additional way to disable this invalidation? We need to upload historical data and run tag rebuild afterward.

0 Likes

#2

Hmmm. AsyncProcessingDisabled always worked for us - nothing in the queues at all. You set it to true and confirmed that the entry got merged, right?

0 Likes

#3

Yes the config seems to be correctly set :

But we have tons of new calcfields entries:

0 Likes

#4

This is very odd. My only theory is that the previous TenantConfig value got cached and the change somehow did not propagate to some of the workers. If that is the case, Cluster.emptyAllCaches() may work.

@trothwein FYI

0 Likes

#5

I don’t think it is a cache problem, I’ve run a tunneled TenantConfig.get on each node I get true each time.

0 Likes