txn_index_catalog_changes.js has a session object that goes out of scope before consistency checks are performed. When performing these consistency checks, we do an fsync lock. When the session object is garbage collected, it will try to run abortTransaction. If this occurs while the server is fsync locked, we can get stuck because the abortTransaction must wait for current optime to be majority committed before responding with NoSuchTransaction.