Add comment describing why commit() should not be called during replay.

1 files changed, 7 insertions, 0 deletions

diff --git a/searchcore/src/vespa/searchcore/proton/server/documentdb.cpp b/searchcore/src/vespa/searchcore/proton/server/documentdb.cpp
index 20f8853a722..c63785faa35 100644
--- a/searchcore/src/vespa/searchcore/proton/server/documentdb.cpp
+++ b/searchcore/src/vespa/searchcore/proton/server/documentdb.cpp
@@ -911,6 +911,13 @@ DocumentDB::syncFeedView()
     IFeedView::SP newFeedView(_subDBs.getFeedView());
 
     _writeService.sync();
+    /*
+     * Don't call commit() on visibility handler during transaction
+     * log replay since the serial number used for the commit will be
+     * too high until the replay is complete. This check can be
+     * removed again when feed handler has improved tracking of serial
+     * numbers during replay.
+     */
     if (_state.getAllowReconfig()) {
         _visibility.commit();
     }