Paul Rogers created DRILL-8102:
----------------------------------
Summary: Tests use significant space outside the drill directory
Key: DRILL-8102
URL: https://issues.apache.org/jira/browse/DRILL-8102
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.19.0
Reporter: Paul Rogers
I use a Linux Mint (Ubuntu) machine in which the root file system has limited
space, but /user has a large amount of space. My Drill build directory is
within my home directory in /user. Most tests write to the various target
folders within the Drill directory, which ensures that each test is isolated,
and that test files are removed in a {{{}mvn clean{}}}.
However, it appears that some tests, perhaps Cassandra, ElasticSearch or Spunk,
write to directories outside of Drill, perhaps to /tmp, /var, etc. The result
is that, each time I run the tests, I get low disk-space warnings on my root
file system. In the worst case, the tests fail due to lack of disk space.
Since it is not clear where the files are written, it is not clear what I
should clean up, or how I might add a sym link to a location with more space.
(Yes, I could get a bigger SSD, and rebuild my root file system, but I'm
lazy...)
As a general rule, all Drill tests should write to a target directory. If that
is not possible, then clearly state somewhere what directories are used so that
sufficient space can be provided, and we know where to go clean up files once
the build runs.
Perhaps some of the tests start Docker containers? If so, then, again, it
should be made clear how much cache space Docker will require.
Another suggestion is to change the build order. Those tests which require
external resources should occur last, after all the others (UDFs, Syslog, etc.)
which require only Drill. That way, if failures occur in the external systems,
we at least know the core Drill modules work.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
