Thanks, for the patch Steve Loughran.
-that is too small will result in either too many jobs being submitted
-for efficient work, or the `JobSubmissionClient` running out of memory.
+that is too small will result in badly partitioned workload.
Your change here correctly states the root effect, whereas what you're removing states the visible side effects. Seems to me that they're both useful. Maybe add your statement with the existing statement as a clarifying subordinate phrase?
assertPathExists("expected path to be visible before anything written",
I don't understand the message here. Didn't you just write 'a' and then flush it?
assertTrue("fs.getDefaultBlockSize(path) size is invalid " + defaultBlockSize,
defaultBlockSize > 0);
Would it be helpful here to replace path with the actual path?
* @param parent Test file parent dir path
* thrown if an I/O error occurs while writing or reading the test file
* <i>other than file not found</i>
* @return the status
* @throws IOException
The throws message does not follow the @throws tag.
In the getFileStatusEventually() method, would it be better to include a short (~10ms) sleep to reduce the impact during parallel testing?