Does the max queue size setting for nHaystack in the Tridium AX correspond with the size of the number of histories that nHaystack can serve?

I am working on a customer with more than 30k histories, yet only 7k of the histories are being published by nHaystack. I'm hoping increasing this max queue size will resolve this problem.

Jerry

maxQueueSize is used to control the number of queued-up requests in an AX Worker. The default value of 5000 is actually quite high, although I suppose it wouldn't hurt to experiment with it.

Are you talking about exporting histories via BNHaystackService, or importing them with the driver, using BNHaystackServer?

Mike, Thanks for the elaboration, it sounds like the maxQueueSize setting doesn't apply to my issue.

I believe we are using the nHaystackService. We have all the histories stored on a Tridium AX, and I ultimately sync all of the histories to equivalent points in a SkySpark server on a separate machine, through the Haystack connector.

I noticed recently that some points on the SkySpark side didn't receive any of the historical data stored in the equivalent history in Tridium, so I thought there may be a limit to the size of the nHaystack cache of stored histories.

Looking over my SkySpark history import code, I also applied a start date of the history data, and some of the histories that didn't come in only had data that was before the start date. Thus, I'm going to do a re-sync of the history data with an earlier start date and see if all the histories come in now.

I'll let you know if I continue to have history import issues afterward.