HADOOP-15999. S3Guard: Better support for out-of-band operations.

Author:    Gabor Bota

hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/contract/AbstractContractGetFileStatusTest.java

@@ -22,6 +22,7 @@
 import java.io.IOException;
 import java.util.Arrays;
 import java.util.List;
+import java.util.UUID;
 
 import org.apache.hadoop.fs.FileStatus;
 import org.apache.hadoop.fs.FileSystem;
@@ -395,7 +396,8 @@ private Path createDirWithEmptySubFolder() throws IOException {
     Path path = getContract().getTestPath();
     fs.delete(path, true);
     // create a - non-qualified - Path for a subdir
-    Path subfolder = path.suffix('/' + this.methodName.getMethodName());
+    Path subfolder = path.suffix('/' + this.methodName.getMethodName()
+        + "-" + UUID.randomUUID());
     mkdirs(subfolder);
     return subfolder;
   }

hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/Constants.java

@@ -545,7 +545,7 @@ private Constants() {
   public static final String S3GUARD_METASTORE_LOCAL_ENTRY_TTL =
       "fs.s3a.s3guard.local.ttl";
   public static final int DEFAULT_S3GUARD_METASTORE_LOCAL_ENTRY_TTL
-      = 10 * 1000;
+      = 60 * 1000;
 
   /**
    * Use DynamoDB for the metadata: {@value}.

hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java

@@ -1343,6 +1343,16 @@ public boolean hasMetadataStore() {
     return !S3Guard.isNullMetadataStore(metadataStore);
   }
 
+  /**
+   * Does the filesystem have an authoritative metadata store?
+   * @return true if there is a metadata store and the authoritative flag
+   * is set for this filesystem.
+   */
+  @VisibleForTesting
+  boolean hasAuthoritativeMetadataStore() {
+    return hasMetadataStore() && allowAuthoritative;
+  }
+
   /**
    * Get the metadata store.
    * This will always be non-null, but may be bound to the
@@ -2370,6 +2380,38 @@ S3AFileStatus innerGetFileStatus(final Path f,
             "deleted by S3Guard");
       }
 
+      // if ms is not authoritative, check S3 if there's any recent
+      // modification - compare the modTime to check if metadata is up to date
+      // Skip going to s3 if the file checked is a directory. Because if the
+      // dest is also a directory, there's no difference.
+      // TODO After HADOOP-16085 the modification detection can be done with
+      //  etags or object version instead of modTime
+      if (!pm.getFileStatus().isDirectory() &&
+          !allowAuthoritative) {
+        LOG.debug("Metadata for {} found in the non-auth metastore.", path);
+        final long msModTime = pm.getFileStatus().getModificationTime();
+
+        S3AFileStatus s3AFileStatus;
+        try {
+          s3AFileStatus = s3GetFileStatus(path, key, tombstones);
+        } catch (FileNotFoundException fne) {
+          s3AFileStatus = null;
+        }
+        if (s3AFileStatus == null) {
+          LOG.warn("Failed to find file {}. Either it is not yet visible, or "
+              + "it has been deleted.", path);
+        } else {
+          final long s3ModTime = s3AFileStatus.getModificationTime();
+
+          if(s3ModTime > msModTime) {
+            LOG.debug("S3Guard metadata for {} is outdated, updating it",
+                path);
+            return S3Guard.putAndReturn(metadataStore, s3AFileStatus,
+                instrumentation);
+          }
+        }
+      }
+
       FileStatus msStatus = pm.getFileStatus();
       if (needEmptyDirectoryFlag && msStatus.isDirectory()) {
         if (pm.isEmptyDirectory() != Tristate.UNKNOWN) {

hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/S3Guard.java

@@ -24,7 +24,9 @@
 import java.util.ArrayList;
 import java.util.Collection;
 import java.util.List;
+import java.util.Map;
 import java.util.Set;
+import java.util.stream.Collectors;
 
 import com.google.common.annotations.VisibleForTesting;
 import com.google.common.base.Preconditions;
@@ -184,6 +186,9 @@ public static FileStatus[] dirMetaToStatuses(DirListingMetadata dirMeta)  {
    *
    * Also update the MetadataStore to reflect the resulting directory listing.
    *
+   * In not authoritative case: update file metadata if mod_time in listing
+   * of a file is greater then what is currently in the ms
+   *
    * @param ms MetadataStore to use.
    * @param path path to directory
    * @param backingStatuses Directory listing from the backing store.
@@ -219,13 +224,26 @@ public static FileStatus[] dirListingUnion(MetadataStore ms, Path path,
     // Since the authoritative case is already handled outside this function,
     // we will basically start with the set of directory entries in the
     // DirListingMetadata, and add any that only exist in the backingStatuses.
-
     boolean changed = false;
+    final Map<Path, FileStatus> dirMetaMap = dirMeta.getListing().stream()
+        .collect(Collectors.toMap(
+            pm -> pm.getFileStatus().getPath(), PathMetadata::getFileStatus)
+        );
+
     for (FileStatus s : backingStatuses) {
       if (deleted.contains(s.getPath())) {
         continue;
       }
 
+      if (!isAuthoritative){
+        FileStatus status = dirMetaMap.get(s.getPath());
+        if (status != null
+            && s.getModificationTime() > status.getModificationTime()) {
+          LOG.debug("Update ms with newer metadata of: {}", status);
+          ms.put(new PathMetadata(s));
+        }
+      }
+
       // Minor race condition here.  Multiple threads could add to this
       // mutable DirListingMetadata.  Since it is backed by a
       // ConcurrentHashMap, the last put() wins.

hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/s3guard.md

@@ -105,8 +105,9 @@ two different reasons:
 
 * Authoritative S3Guard
     * S3Guard can be set as authoritative, which means that an S3A client will
-    avoid round-trips to S3 when **getting directory listings** if there is a fully
-    cached version of the directory stored in metadata store.
+    avoid round-trips to S3 when **getting file metadata**, and **getting
+    directory listings** if there is a fully cached version of the directory
+    stored in metadata store.
     * This mode can be set as a configuration property
     `fs.s3a.metadatastore.authoritative`
     * All interactions with the S3 bucket(s) must be through S3A clients sharing
@@ -128,16 +129,20 @@ two different reasons:
 
 More on Authoritative S3Guard:
 
-* It is not treating the MetadataStore (e.g. dynamodb) as the source of truth
- in general.
-* It is the ability to short-circuit S3 list objects and serve listings from
-the MetadataStore in some circumstances.
+* This setting is about treating the MetadataStore (e.g. dynamodb) as the source
+ of truth in general, and also to short-circuit S3 list objects and serve
+ listings from the MetadataStore in some circumstances.
+* For S3A to skip S3's get object metadata, and serve it directly from the
+MetadataStore, the following things must all be true:
+    1. The S3A client is configured to allow MetadataStore to be authoritative
+    source of a file metadata (`fs.s3a.metadatastore.authoritative=true`).
+    1. The MetadataStore has the file metadata for the path stored in it.
 * For S3A to skip S3's list objects on some path, and serve it directly from
 the MetadataStore, the following things must all be true:
     1. The MetadataStore implementation persists the bit
     `DirListingMetadata.isAuthorititative` set when calling
     `MetadataStore#put` (`DirListingMetadata`)
-    1. The S3A client is configured to allow metadatastore to be authoritative
+    1. The S3A client is configured to allow MetadataStore to be authoritative
     source of a directory listing (`fs.s3a.metadatastore.authoritative=true`).
     1. The MetadataStore has a **full listing for path** stored in it.  This only
     happens if the FS client (s3a) explicitly has stored a full directory
@@ -154,8 +159,9 @@ recommended that you leave the default setting here:
 </property>
 ```
 
-Note that a MetadataStore MAY persist this bit. (Not MUST).
 Setting this to `true` is currently an experimental feature.
+Note that a MetadataStore MAY persist this bit in the directory listings. (Not
+MUST).
 
 Note that if this is set to true, it may exacerbate or persist existing race
 conditions around multiple concurrent modifications and listings of a given
@@ -396,6 +402,48 @@ for two buckets with a shared table, while disabling it for the public
 bucket.
 
 
+### Out-of-band operations with S3Guard
+
+We call an operation out-of-band (OOB) when a bucket is used by a client with
+ S3Guard, and another client runs a write (e.g delete, move, rename,
+ overwrite) operation on an object in the same bucket without S3Guard.
+
+The definition of behaviour in S3AFileSystem/MetadataStore in case of OOBs:
+* A client with S3Guard
+* B client without S3Guard (Directly to S3)
+
+
+* OOB OVERWRITE, authoritative mode:
+  * A client creates F1 file
+  * B client overwrites F1 file with F2 (Same, or different file size)
+  * A client's getFileStatus returns F1 metadata
+
+* OOB OVERWRITE, NOT authoritative mode:
+  * A client creates F1 file
+  * B client overwrites F1 file with F2 (Same, or different file size)
+  * A client's getFileStatus returns F2 metadata. In not authoritative mode we
+ check S3 for the file. If the modification time of the file in S3 is greater
+ than in S3Guard, we can safely return the S3 file metadata and update the
+ cache.
+
+* OOB DELETE, authoritative mode:
+  * A client creates F file
+  * B client deletes F file
+  * A client's getFileStatus returns that the file is still there
+
+* OOB DELETE, NOT authoritative mode:
+  * A client creates F file
+  * B client deletes F file
+  * A client's getFileStatus returns that the file is still there
+
+Note: authoritative and NOT authoritative mode behaves the same at
+OOB DELETE case.
+
+The behaviour in case of getting directory listings:
+* File status in metadata store gets updated during the listing the same way
+as in getFileStatus.
+
+
 ## S3Guard Command Line Interface (CLI)
 
 Note that in some cases an AWS region or `s3a://` URI can be provided.

hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md

@@ -310,7 +310,7 @@ By their very nature they are slow. And, as their execution time is often
 limited by bandwidth between the computer running the tests and the S3 endpoint,
 parallel execution does not speed these tests up.
 
-***Note: Running scale tests with -Ds3guard and -Ddynamo requires that
+***Note: Running scale tests with `-Ds3guard` and `-Ddynamo` requires that
 you use a private, testing-only DynamoDB table.*** The tests do disruptive
 things such as deleting metadata and setting the provisioned throughput
 to very low values.

hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/ITestS3GuardOutOfBandOperations.java

@@ -0,0 +1,633 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.hadoop.fs.s3a;
+
+import java.io.FileNotFoundException;
+import java.io.IOException;
+import java.net.URI;
+import java.util.Arrays;
+import java.util.Collection;
+import java.util.UUID;
+import java.util.stream.Collectors;
+
+import org.junit.Before;
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.junit.runners.Parameterized;
+
+import org.apache.hadoop.fs.FSDataInputStream;
+import org.apache.hadoop.fs.s3a.s3guard.NullMetadataStore;
+import org.apache.hadoop.io.IOUtils;
+import org.apache.hadoop.conf.Configuration;
+import org.apache.hadoop.fs.FileStatus;
+import org.apache.hadoop.fs.Path;
+import org.apache.hadoop.fs.s3a.s3guard.DirListingMetadata;
+import org.apache.hadoop.fs.s3a.s3guard.MetadataStore;
+
+import static org.apache.hadoop.fs.s3a.S3ATestUtils.removeBaseAndBucketOverrides;
+import static org.apache.hadoop.test.LambdaTestUtils.eventually;
+import static org.junit.Assume.assumeTrue;
+import static org.apache.hadoop.fs.contract.ContractTestUtils.writeTextFile;
+import static org.apache.hadoop.fs.s3a.Constants.METADATASTORE_AUTHORITATIVE;
+import static org.apache.hadoop.fs.s3a.Constants.S3_METADATA_STORE_IMPL;
+import static org.apache.hadoop.fs.s3a.S3ATestUtils.metadataStorePersistsAuthoritativeBit;
+import static org.apache.hadoop.test.LambdaTestUtils.intercept;
+
+/**
+ *
+ * This integration test is for documenting and defining how S3Guard should
+ * behave in case of out-of-band (OOB) operations.
+ * <pre>
+ * The behavior is the following in case of S3AFileSystem.getFileStatus:
+ * A client with S3Guard
+ * B client without S3Guard (Directly to S3)
+ *
+ * * OOB OVERWRITE, authoritative mode:
+ * ** A client creates F1 file
+ * ** B client overwrites F1 file with F2 (Same, or different file size)
+ * ** A client's getFileStatus returns F1 metadata
+ *
+ * * OOB OVERWRITE, NOT authoritative mode:
+ * ** A client creates F1 file
+ * ** B client overwrites F1 file with F2 (Same, or different file size)
+ * ** A client's getFileStatus returns F2 metadata. In not authoritative
+ * mode we check S3 for the file. If the modification time of the file in S3
+ * is greater than in S3Guard, we can safely return the S3 file metadata and
+ * update the cache.
+ *
+ * * OOB DELETE, authoritative mode:
+ * ** A client creates F file
+ * ** B client deletes F file
+ * ** A client's getFileStatus returns that the file is still there
+ *
+ * * OOB DELETE, NOT authoritative mode:
+ * ** A client creates F file
+ * ** B client deletes F file
+ * ** A client's getFileStatus returns that the file is still there
+ *
+ * As you can see, authoritative and NOT authoritative mode behaves the same
+ * at OOB DELETE case.
+ *
+ * The behavior is the following in case of S3AFileSystem.listStatus:
+ * * File status in metadata store gets updated during the listing (in
+ * S3Guard.dirListingUnion) the same way as in getFileStatus.
+ * </pre>
+ */
+@RunWith(Parameterized.class)
+public class ITestS3GuardOutOfBandOperations extends AbstractS3ATestBase {
+
+  public static final int TIMESTAMP_SLEEP = 2000;
+
+  public static final int STABILIZATION_TIME = 20_000;
+
+  public static final int PROBE_INTERVAL_MILLIS = 500;
+
+  private S3AFileSystem guardedFs;
+  private S3AFileSystem rawFS;
+
+  private MetadataStore realMs;
+
+  /**
+   * Is the "real" FS Authoritative.
+   */
+  private final boolean authoritative;
+
+  /**
+   * Test array for parameterized test runs.
+   * @return a list of parameter tuples.
+   */
+  @Parameterized.Parameters
+  public static Collection<Object[]> params() {
+    return Arrays.asList(new Object[][]{
+        {true}, {false}
+    });
+  }
+
+  public ITestS3GuardOutOfBandOperations(final boolean authoritative) {
+    this.authoritative = authoritative;
+  }
+
+  /**
+   * By changing the method name, the thread name is changed and
+   * so you can see in the logs which mode is being tested.
+   * @return a string to use for the thread namer.
+   */
+  @Override
+  protected String getMethodName() {
+    return super.getMethodName() +
+        (authoritative ? "-auth" : "-nonauth");
+  }
+
+  @Before
+  public void setup() throws Exception {
+    super.setup();
+    S3AFileSystem fs = getFileSystem();
+    // These test will fail if no ms
+    assumeTrue("FS needs to have a metadatastore.",
+        fs.hasMetadataStore());
+    assumeTrue("Metadatastore should persist authoritative bit",
+        metadataStorePersistsAuthoritativeBit(fs.getMetadataStore()));
+
+    // This test setup shares a single metadata store across instances,
+    // so that test runs with a local FS work.
+    // but this needs to be addressed in teardown, where the guarded fs
+    // needs to be detached from the metadata store before it is closed,
+    realMs = fs.getMetadataStore();
+    // now we create a new FS with the auth parameter
+    guardedFs = createGuardedFS(authoritative);
+    assertTrue("No S3Guard store for " + guardedFs,
+        guardedFs.hasMetadataStore());
+    assertEquals("Authoritative status in " + guardedFs,
+        authoritative, guardedFs.hasAuthoritativeMetadataStore());
+
+    // create raw fs without s3guard
+    rawFS = createUnguardedFS();
+    assertFalse("Raw FS still has S3Guard " + rawFS,
+        rawFS.hasMetadataStore());
+  }
+
+  @Override
+  public void teardown() throws Exception {
+    if (guardedFs != null) {
+      // detach from the (shared) metadata store.
+      guardedFs.setMetadataStore(new NullMetadataStore());
+      // and only then close it.
+      IOUtils.cleanupWithLogger(LOG, guardedFs);
+    }
+    IOUtils.cleanupWithLogger(LOG, rawFS);
+    super.teardown();
+  }
+
+  /**
+   * Create a new FS which is the same config as the test FS, except
+   * that it is guarded with the specific authoritative mode.
+   * @param authoritativeMode mode of the new FS's metastore
+   * @return the new FS
+   */
+  private S3AFileSystem createGuardedFS(boolean authoritativeMode)
+      throws Exception {
+    S3AFileSystem testFS = getFileSystem();
+    Configuration config = new Configuration(testFS.getConf());
+    URI uri = testFS.getUri();
+
+    removeBaseAndBucketOverrides(uri.getHost(), config,
+        METADATASTORE_AUTHORITATIVE);
+    config.setBoolean(METADATASTORE_AUTHORITATIVE, authoritativeMode);
+    final S3AFileSystem gFs = createFS(uri, config);
+    // set back the same metadata store instance
+    gFs.setMetadataStore(realMs);
+    return gFs;
+  }
+
+  /**
+   * Create a test filesystem which is always unguarded.
+   * This filesystem MUST be closed in test teardown.
+   * @return the new FS
+   */
+  private S3AFileSystem createUnguardedFS() throws Exception {
+    S3AFileSystem testFS = getFileSystem();
+    Configuration config = new Configuration(testFS.getConf());
+    URI uri = testFS.getUri();
+
+    removeBaseAndBucketOverrides(uri.getHost(), config,
+        S3_METADATA_STORE_IMPL);
+    removeBaseAndBucketOverrides(uri.getHost(), config,
+        METADATASTORE_AUTHORITATIVE);
+    return createFS(uri, config);
+  }
+
+  /**
+   * Create and initialize a new filesystem.
+   * This filesystem MUST be closed in test teardown.
+   * @param uri FS URI
+   * @param config config.
+   * @return new instance
+   * @throws IOException failure
+   */
+  private S3AFileSystem createFS(final URI uri, final Configuration config)
+      throws IOException {
+    S3AFileSystem fs2 = new S3AFileSystem();
+    fs2.initialize(uri, config);
+    return fs2;
+  }
+
+  @Test
+  public void testSameLengthOverwrite() throws Exception {
+    String firstText = "hello, world!";
+    String secondText = "HELLO, WORLD!";
+    overwriteFile(firstText, secondText);
+  }
+
+  @Test
+  public void testLongerLengthOverwrite() throws Exception {
+    String firstText = "Hello, World!";
+    String secondText = firstText + " " + firstText;
+    overwriteFile(firstText, secondText);
+  }
+
+  @Test
+  public void testOutOfBandDeletes() throws Exception {
+    Path testFileName = path("OutOfBandDelete-" + UUID.randomUUID());
+    outOfBandDeletes(testFileName, authoritative);
+  }
+
+  @Test
+  public void testListingSameLengthOverwrite() throws Exception {
+    overwriteFileInListing("THE TEXT", "the text");
+  }
+
+  @Test
+  public void testListingLongerLengthOverwrite() throws Exception {
+    overwriteFileInListing("THE TEXT", "THE LONGER TEXT");
+  }
+
+  @Test
+  public void testListingDelete() throws Exception {
+    deleteFileInListing();
+  }
+
+  /**
+   * Perform an out-of-band delete.
+   * @param testFilePath filename
+   * @param allowAuthoritative  is the store authoritative
+   * @throws Exception failure
+   */
+  private void outOfBandDeletes(
+      final Path testFilePath,
+      final boolean allowAuthoritative)
+      throws Exception {
+    try {
+      // Create initial file
+      String text = "Hello, World!";
+      writeTextFile(guardedFs, testFilePath, text, true);
+      awaitFileStatus(rawFS, testFilePath);
+
+      // Delete the file without S3Guard (raw)
+      deleteFile(rawFS, testFilePath);
+
+      // The check is the same if s3guard is authoritative and if it's not
+      // it should be in the ms
+      FileStatus status = guardedFs.getFileStatus(testFilePath);
+      LOG.info("Authoritative: {} status path: {}",
+          allowAuthoritative, status.getPath());
+      expectExceptionWhenReading(testFilePath, text);
+      expectExceptionWhenReadingOpenFileAPI(testFilePath, text);
+    } finally {
+      guardedFs.delete(testFilePath, true);
+    }
+  }
+
+  /**
+   * Overwrite a file out of band.
+   * @param firstText first text
+   * @param secondText second text
+   * @throws Exception failure
+   */
+  private void overwriteFile(String firstText, String secondText)
+      throws Exception {
+    boolean allowAuthoritative = authoritative;
+    Path testFilePath = path("OverwriteFileTest-" + UUID.randomUUID());
+    LOG.info("Allow authoritative param: {}",  allowAuthoritative);
+    try {
+      // Create initial file
+      writeTextFile(
+          guardedFs, testFilePath, firstText, true);
+      // and cache the value for later
+      final FileStatus origStatus = awaitFileStatus(rawFS, testFilePath);
+      waitForDifferentTimestamps();
+      // Overwrite the file without S3Guard
+      writeTextFile(
+          rawFS, testFilePath, secondText, true);
+
+      // Read the file and verify the data
+      eventually(STABILIZATION_TIME, PROBE_INTERVAL_MILLIS,
+          () -> {
+            FileStatus rawFileStatus = rawFS.getFileStatus(testFilePath);
+            final FileStatus guardedFileStatus =
+                guardedFs.getFileStatus(testFilePath);
+            verifyFileStatusAsExpected(firstText, secondText,
+                allowAuthoritative,
+                origStatus,
+                rawFileStatus,
+                guardedFileStatus);
+          });
+    } finally {
+      guardedFs.delete(testFilePath, true);
+    }
+  }
+
+  /**
+   * Assert that an array has a given size; in failure the full string values
+   * of the array will be included, one per line.
+   * @param message message for errors.
+   * @param expected expected length.
+   * @param array the array to probe
+   */
+  private <T> void assertArraySize(
+      final String message,
+      final int expected,
+      final T[] array) {
+    if (expected != array.length) {
+      // condition is not met, build an error which includes all the entries
+      String listing = Arrays.stream(array)
+          .map(Object::toString)
+          .collect(Collectors.joining("\n"));
+      fail(message + ": expected " + expected + " elements but found "
+          + array.length
+          + "\n" + listing);
+    }
+  }
+
+  /**
+   * Overwrite a file, verify that the text is different as is the timestamp.
+   * There are some pauses in the test to ensure that timestamps are different.
+   * @param firstText first text to write
+   * @param secondText second text to write
+   */
+  private void overwriteFileInListing(String firstText, String secondText)
+      throws Exception {
+    boolean allowAuthoritative = authoritative;
+
+    LOG.info("Authoritative mode enabled: {}", allowAuthoritative);
+    String rUUID = UUID.randomUUID().toString();
+    String testDir = "dir-" + rUUID + "/";
+    String testFile = testDir + "file-1-" + rUUID;
+    Path testDirPath = path(testDir);
+    Path testFilePath = guardedFs.qualify(path(testFile));
+
+    try {
+      // Create initial statusIterator with guarded ms
+      writeTextFile(guardedFs, testFilePath, firstText, true);
+      // and cache the value for later
+      final FileStatus origStatus = awaitFileStatus(rawFS, testFilePath);
+
+      // Do a listing to cache the lists. Should be authoritative if it's set.
+      final FileStatus[] origList = guardedFs.listStatus(testDirPath);
+      assertArraySize("Added one file to the new dir, so the number of "
+              + "files in the dir should be one.", 1, origList);
+      final DirListingMetadata dirListingMetadata =
+          realMs.listChildren(guardedFs.qualify(testDirPath));
+      assertListingAuthority(allowAuthoritative, dirListingMetadata);
+
+      // a brief pause to guarantee timestamps are different.
+      waitForDifferentTimestamps();
+
+      // Update file with second text without S3Guard (raw)
+      deleteFile(rawFS, testFilePath);
+
+      // write to the test path with the second text
+      writeTextFile(rawFS, testFilePath, secondText, true);
+      // and await it becoming visible again.
+      final FileStatus rawFileStatus = awaitFileStatus(rawFS, testFilePath);
+
+      // check listing in guarded store.
+      final FileStatus[] modList = guardedFs.listStatus(testDirPath);
+      assertArraySize("Added one file to the new dir then modified it, "
+          + "so the number of files in the dir should be one.", 1,
+          modList);
+      assertEquals("The only file path in the directory listing should be "
+              + "equal to the testFilePath.", testFilePath,
+          modList[0].getPath());
+
+      // Read the file and verify the data
+      eventually(STABILIZATION_TIME, PROBE_INTERVAL_MILLIS,
+          () -> {
+            final FileStatus guardedFileStatus =
+                guardedFs.getFileStatus(testFilePath);
+            verifyFileStatusAsExpected(firstText, secondText,
+                allowAuthoritative,
+                origStatus,
+                rawFileStatus,
+                guardedFileStatus);
+          });
+    } finally {
+      guardedFs.delete(testDirPath, true);
+    }
+  }
+
+  private void deleteFile(final S3AFileSystem fs, final Path testFilePath)
+      throws Exception {
+    fs.delete(testFilePath, true);
+    awaitDeletedFileDisappearance(fs, testFilePath);
+  }
+
+
+  /**
+   * Verify that the file status of a file which has been overwritten
+   * is as expected, throwing informative exceptions if not.
+   * @param firstText text of the first write
+   * @param secondText text of the second
+   * @param allowAuthoritative is S3Guard being authoritative
+   * @param origStatus filestatus of the first written file
+   * @param rawFileStatus status of the updated file from the raw FS
+   * @param guardedFileStatus status of the updated file from the guarded FS
+   */
+  private void verifyFileStatusAsExpected(final String firstText,
+      final String secondText,
+      final boolean allowAuthoritative,
+      final FileStatus origStatus,
+      final FileStatus rawFileStatus,
+      final FileStatus guardedFileStatus) {
+    String stats = "\nRaw: " + rawFileStatus.toString() +
+        "\nGuarded: " + guardedFileStatus.toString();
+    if (firstText.length() != secondText.length()) {
+      // the file lengths are different, so compare that first.
+      // it's not going to be brittle to timestamps, and easy to understand
+      // when there is an error.
+
+      // check the file length in the raw FS To verify that status is actually
+      // stabilized w.r.t the last write.
+      long expectedLength = secondText.length();
+      assertEquals("Length of raw file status did not match the updated text "
+              + rawFileStatus,
+          expectedLength, rawFileStatus.getLen());
+      // now compare the lengths of the the raw and guarded files
+      long guardedLength = guardedFileStatus.getLen();
+      if (allowAuthoritative) {
+        // expect the length to be out of sync
+        assertNotEquals(
+            "File length in authoritative table with " + stats,
+            expectedLength, guardedLength);
+      } else {
+        assertEquals(
+            "File length in authoritative table with " + stats,
+            expectedLength, guardedLength);
+      }
+    }
+    // Next: modification time.
+    long rawModTime = rawFileStatus.getModificationTime();
+    long guardedModTime = guardedFileStatus.getModificationTime();
+    assertNotEquals(
+        "Updated file still has original timestamp\n"
+            + " original " + origStatus + stats,
+        origStatus.getModificationTime(), rawModTime);
+    if (allowAuthoritative) {
+      // If authoritative is allowed metadata is not updated, so mod_time
+      // won't match
+      assertNotEquals("Authoritative is enabled, so metadata is not "
+              + "updated in ms, so mod_time won't match. Expecting "
+              + "different values for raw and guarded filestatus."
+              + stats,
+          rawModTime,
+          guardedModTime);
+    } else {
+      // If authoritative is not enabled metadata is updated, mod_time
+      // will match
+      assertEquals("Authoritative is disabled, so metadata is"
+              + " updated in ms, so mod_time must match. Expecting "
+              + " same values for raw and guarded filestatus."
+              + stats,
+          rawModTime,
+          guardedModTime);
+    }
+  }
+
+  /**
+   * A brief pause to guarantee timestamps are different.
+   * This doesn't have to be as long as a stabilization delay.
+   */
+  private void waitForDifferentTimestamps() throws InterruptedException {
+    Thread.sleep(TIMESTAMP_SLEEP);
+  }
+
+  /**
+   * Assert that a listing has the specific authority.
+   * @param expectAuthoritative expect authority bit of listing
+   * @param dirListingMetadata listing to check
+   */
+  private void assertListingAuthority(final boolean expectAuthoritative,
+      final DirListingMetadata dirListingMetadata) {
+    if (expectAuthoritative) {
+      assertTrue("DirListingMeta should be authoritative if authoritative "
+              + "mode is enabled.",
+          dirListingMetadata.isAuthoritative());
+    } else {
+      assertFalse("DirListingMeta should not be authoritative if "
+              + "authoritative mode is disabled.",
+          dirListingMetadata.isAuthoritative());
+    }
+  }
+
+  /**
+   * Delete a file and use listStatus to build up the S3Guard cache.
+   */
+  private void deleteFileInListing()
+      throws Exception {
+
+    boolean allowAuthoritative = authoritative;
+    LOG.info("Authoritative mode enabled: {}", allowAuthoritative);
+    String rUUID = UUID.randomUUID().toString();
+    String testDir = "dir-" + rUUID + "/";
+    String testFile = testDir + "file-1-" + rUUID;
+    Path testDirPath = path(testDir);
+    Path testFilePath = guardedFs.qualify(path(testFile));
+    String text = "Some random text";
+
+    try {
+      // Create initial statusIterator with real ms
+      writeTextFile(
+          guardedFs, testFilePath, text, true);
+      awaitFileStatus(rawFS, testFilePath);
+
+      // Do a listing to cache the lists. Should be authoritative if it's set.
+      final FileStatus[] origList = guardedFs.listStatus(testDirPath);
+      assertEquals("Added one file to the new dir, so the number of "
+          + "files in the dir should be one.", 1, origList.length);
+      final DirListingMetadata dirListingMetadata =
+          realMs.listChildren(guardedFs.qualify(testDirPath));
+      assertListingAuthority(allowAuthoritative, dirListingMetadata);
+
+      // Delete the file without S3Guard (raw)
+      deleteFile(rawFS, testFilePath);
+
+      // File status will be still readable from s3guard
+      FileStatus status = guardedFs.getFileStatus(testFilePath);
+      LOG.info("authoritative: {} status: {}", allowAuthoritative, status);
+      expectExceptionWhenReading(testFilePath, text);
+      expectExceptionWhenReadingOpenFileAPI(testFilePath, text);
+    } finally {
+      guardedFs.delete(testDirPath, true);
+    }
+  }
+
+  /**
+   * We expect the read to fail with an FNFE: open will be happy.
+   * @param testFilePath path of the test file
+   * @param text the context in the file.
+   * @throws Exception failure other than the FNFE
+   */
+  private void expectExceptionWhenReading(Path testFilePath, String text)
+      throws Exception {
+    try (FSDataInputStream in = guardedFs.open(testFilePath)) {
+      intercept(FileNotFoundException.class, () -> {
+        byte[] bytes = new byte[text.length()];
+        return in.read(bytes, 0, bytes.length);
+      });
+    }
+  }
+
+  /**
+   * We expect the read to fail with an FNFE: open will be happy.
+   * @param testFilePath path of the test file
+   * @param text the context in the file.
+   * @throws Exception failure other than the FNFE
+   */
+  private void expectExceptionWhenReadingOpenFileAPI(
+      Path testFilePath, String text)
+      throws Exception {
+    try (
+        FSDataInputStream in = guardedFs.openFile(testFilePath).build().get()
+    ) {
+      intercept(FileNotFoundException.class, () -> {
+        byte[] bytes = new byte[text.length()];
+        return in.read(bytes, 0, bytes.length);
+      });
+    }
+  }
+
+  /**
+   * Wait for a deleted file to no longer be visible.
+   * @param fs filesystem
+   * @param testFilePath path to query
+   * @throws Exception failure
+   */
+  private void awaitDeletedFileDisappearance(final S3AFileSystem fs,
+      final Path testFilePath) throws Exception {
+    eventually(
+        STABILIZATION_TIME, PROBE_INTERVAL_MILLIS,
+        () -> intercept(FileNotFoundException.class,
+            () -> fs.getFileStatus(testFilePath)));
+  }
+
+  /**
+   * Wait for a file to be visible.
+   * @param fs filesystem
+   * @param testFilePath path to query
+   * @return the file status.
+   * @throws Exception failure
+   */
+  private FileStatus awaitFileStatus(S3AFileSystem fs,
+      final Path testFilePath)
+      throws Exception {
+    return eventually(
+        STABILIZATION_TIME, PROBE_INTERVAL_MILLIS,
+        () -> fs.getFileStatus(testFilePath));
+  }
+
+}