HADOOP-13599. s3a close() to be non-synchronized, so avoid risk of deadlock on shutdown. Contributed by Steve Loughran.

(cherry picked from commit 47f80922dc)
This commit is contained in:
Chris Nauroth 2016-09-28 15:53:17 -07:00
parent a7c1636296
commit 1f1e47e411
2 changed files with 14 additions and 1 deletions

View File

@ -124,6 +124,7 @@ public class S3AFileSystem extends FileSystem {
private S3AInputPolicy inputPolicy;
private static final AtomicBoolean warnedOfCoreThreadDeprecation =
new AtomicBoolean(false);
private final AtomicBoolean closed = new AtomicBoolean(false);
// The maximum number of entries that can be deleted in any call to s3
private static final int MAX_ENTRIES_TO_DELETE = 1000;
@ -1423,7 +1424,11 @@ public class S3AFileSystem extends FileSystem {
* @throws IOException IO problem
*/
@Override
public synchronized void close() throws IOException {
public void close() throws IOException {
if (closed.getAndSet(true)) {
// already closed
return;
}
try {
super.close();
} finally {

View File

@ -409,6 +409,14 @@ public class ITestS3AConfiguration {
awsConf.getUserAgent());
}
@Test
public void testCloseIdempotent() throws Throwable {
conf = new Configuration();
fs = S3ATestUtils.createTestFileSystem(conf);
fs.close();
fs.close();
}
/**
* Reads and returns a field from an object using reflection. If the field
* cannot be found, is null, or is not the expected type, then this method