We’re using index-pull to generate reports, using avet on an inst attribute. For larger date ranges (year at a time in this case), we are seeing this exception:
Execution error (ExceptionInfo) at datomic.client.api.async/ares (async.clj:58).\nSpecified iterator was dropped\n"
after running for 30 or so minutes (and there were multiple running). Sounds like some resource on the server is getting cleaned up before we’re done. We had been thinking about chopping this process up, so that it was always dealing with some time frame we knew was manageable - a day or week for example - and then aggregating those results, but I wanted to check in and make sure there wasn’t something else we were missing.
Does that sound like a reasonable strategy for avoiding this exception?
I’ve been experimenting with iterating over the same time range by breaking the range up into days, starting an index-pull at the beginning of each day and taking while we’re still in that day. This works, but I periodically get
Specified iterator was dropped errors doing this as well. I could retry these, because the time frame is smaller, but I don’t know how to gauge if starting so many iterators is a problem.
Is this problem related to the size of the index?