Cannot save data to cache file
I've been seeing this error show up more frequently in my logs. "Analysis: Cannot save data to cache file" with the name and location of the file. The odd part is that it can. If I restart the report it'll either pick up where it left off or start again and not error.
If there is enough disk space, I still recommend you to disable this option and check if the error appears again.
The drive being written to has around 3TB free so no issues there.
We could try switching off the "Log Details" although that was one of the primary factors in choosing weblog in the first place so losing it would almost defeat the object of the analysis.
Also presumably even if disabled, this might seems to suggest that we might hit a point where the data fails to write.
Is there actually a known issue here relating to the size of cache being written? and if so is there any active development work being down to work around it? (either upping the limit or allowing the data to be split over multiple files etc?)
Windows Server 2012 R2
WebLog Expert 8.6 Enterprise
Output to Web Server
Does the problem always occurs when you analyze this profile? Does it occur if you limit the analysis to one month only? What is the total size of logs you analyze?
If I attempt to run on the full set of data (Currently around 9 weeks (1st Jan 2015 to Yesterday)) it fails every time at the same point as it writes the final data back.
I tried last night, removing the option to "include detailed log data" and the report completed successfully.
So in summary only seems to be an issue with the detailed data included and only happens on large volumes of data and at the very end of the analysis (does that make sense? is the write back of the detailed data something which happens at the very end of the analysis?)
The particular site being analysed by this profile produces IIS logs of around 6GB per day uncompressed (2 web servers load balanced producing 3GBs of logs each) the logs are bz2 compressed for shipping and analysis coming down to around 300MB per day per server.
My concerns here are that we need to achieve a rolling 12 month analysis, so while for the bigger profiles we could drop the detailed data, I am still nervous that we are going to hit another point in time where the output fails due to size (unless it is the case that the apparent limitation only applies to the detailed data)
An alternative which would probably suit us 99% of the time would be to have an extra option to include "some" detailed data. so that whenever the data is analysed the last 7days or adjustable period of detailed data is there but not for the older data.
This would allow us to dig deeper over the most recent content but still retain the lighter version of the historic data without having to have multiple profiles per site? (We have around 60 sites to report on, of which maybe 10-15 are of similar or even greater volume than the one in this case)