diff options
author | Alex Gorrod <alexander.gorrod@mongodb.com> | 2017-09-01 11:43:05 +1000 |
---|---|---|
committer | Michael Cahill <michael.cahill@mongodb.com> | 2017-09-01 11:43:05 +1000 |
commit | e2c927fa58e275468909deae274ad245e3696a3c (patch) | |
tree | 35c93400344b96d8a22a43f91dd83c65916c1bed | |
parent | bacc9ada53a46128642343c162a993d15bc80b57 (diff) | |
download | mongo-e2c927fa58e275468909deae274ad245e3696a3c.tar.gz |
WT-3558 Disable metadata visibility assertion in checkpoints (#3638)mongodb-3.5.13
It is better to return a WT_ROLLBACK so the checkpoint can be retried.
-rw-r--r-- | src/txn/txn_ckpt.c | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/src/txn/txn_ckpt.c b/src/txn/txn_ckpt.c index e54ec99b590..9b6070b1db1 100644 --- a/src/txn/txn_ckpt.c +++ b/src/txn/txn_ckpt.c @@ -309,7 +309,17 @@ __wt_checkpoint_get_handles(WT_SESSION_IMPL *session, const char *cfg[]) ret = __wt_curfile_insert_check(meta_cursor); if (ret == WT_ROLLBACK) { metadata_race = true; + /* + * Disable this check and assertion for now - it is + * possible that a schema operation with a timestamp in + * the future is in the metadata, but not part of the + * the checkpoint now that checkpoints can be created + * at the stable timestamp. + * See WT-3559 for context on re-adding this assertion. + */ +#if 0 ret = 0; +#endif } else metadata_race = false; WT_TRET(__wt_metadata_cursor_release(session, &meta_cursor)); |