[BOOKKEEPER-845] test case fail with error "Unable to delete directory /tmp/bkTest.dir/current/0"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Assignee: Jia Zhai
• Reporter: Jia Zhai
• Created: 17/Mar/15 08:17
• Updated: 01/Jun/15 04:55
• Resolved: 01/Jun/15 04:55

Description

Recently, test case org.apache.bookkeeper.bookie.CompactionTest.testCompactionSafety would fail in "Hadoop QA"'s comments for target patch.
It happened at least in BOOKKEEPER-834 and BOOKKEEPER-839.

The failure is like this:
java.io.IOException: Unable to delete directory /tmp/bkTest1550867777962713274.dir/current/0.
at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1337)
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1910)
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1399)
at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1331)
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1910)
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1399)
at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1331)
at org.apache.bookkeeper.test.BookKeeperClusterTestCase.cleanupTempDirs(BookKeeperClusterTestCase.java:186)
at org.apache.bookkeeper.test.BookKeeperClusterTestCase.tearDown(BookKeeperClusterTestCase.java:114)
2015-03-15 00:48:08,671 - WARN - [BookieJournal-15017:Journal@927] - Journal exits when shutting down
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2052)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
at org.apache.bookkeeper.bookie.Journal.run(Journal.java:822)
2015-03-15 00:48:08,671 - INFO - [BookieJournal-15017:Journal@936] - Journal exited loop!

It seems bookie.Journal.run() not release file when interrupt comes, which is similar to
BOOKKEEPER-838 .
I would like to investigate more on this issue.

Issue Links

• duplicates: BOOKKEEPER-838 ForceWriteThread::run() leaks “logFile.close()” when interrupt comes