Data360 Analyze

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

First time we have seen this error and we had finished stress testing by running 6 dataflows with multiple nodes. We could get in to Data3Sixty but when selecting any Dataflow any and all users received this error. We bounced Data3Sixty and now dataflows are "loading" but not loaded. 

Attached files

Data360_IndexWriter error.png

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

After bouncing Data3Sixty we were able to access dataflows. Upon further research the log files showed

2019-06-05 09:38:06 INFO  root:747 - Error closing reader for a Lucene index: No space left on device

java.io.IOException: No space left on device

The executions directory which shows all the dataflow runs that have been executed was the main culprit in eating up the space.  We need to work on space management of the specific directory and also set up some Linux scripts to warn us of space issues

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Hi Donald, as the error suggests your server has run out of space. When you run data flows a lot of temp files are created that you might not need after a certain amount of days. Attached is a very basic data flow that will read everything in your D3SA temp directory and delete files that are over x amount of days old, as specified by the Days run parameter. You can schedule it to run weekly and it should help manage that side of it. Of course if you're uploading or writing out large Excel files that's something else that might be taking up space. You could expand this data flow to handle other directories and think about what time frame works for you to clean out files and ensure you're not hitting your space limit regularly.

Attached files

Delete Temp Files.lna

Hi Gerry, after deleting temp files, the error still shows again. Does Data3Sixty has purge data process to free up space in the server? Or maybe is there other problems that could cause this error?