diff options
author | Geir Storli <geirst@yahooinc.com> | 2023-02-17 13:31:03 +0000 |
---|---|---|
committer | Geir Storli <geirst@yahooinc.com> | 2023-02-17 13:31:03 +0000 |
commit | ae57d013d59fafca8e0dd956ea3b5cfc949a7319 (patch) | |
tree | 004286d0a702128a49802528eccf8624b496318d | |
parent | 83ddd006f2119fe7321c050ea08533ca6f62b1c0 (diff) |
Update reconfig documentation.
-rw-r--r-- | searchcore/src/vespa/searchcore/proton/server/document_db_reconfig.h | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/searchcore/src/vespa/searchcore/proton/server/document_db_reconfig.h b/searchcore/src/vespa/searchcore/proton/server/document_db_reconfig.h index 9462c018cc2..8d2701f430f 100644 --- a/searchcore/src/vespa/searchcore/proton/server/document_db_reconfig.h +++ b/searchcore/src/vespa/searchcore/proton/server/document_db_reconfig.h @@ -12,15 +12,17 @@ class DocumentSubDBReconfig; * Class representing the result of the prepare step of a DocumentDB reconfig. * * The reconfig is performed in three steps: - * Prepare: + * 1) Prepare: * Based on the config that is changed, new components are instantiated in each subdb. - * This can be costly and is handled by helper threads from the shared executor pool. + * This can be costly and is done by the proton reconfigure thread. * - * Complete prepare: - * Docid limit and serial number are used to complete prepared reconfig. + * 2) Complete prepare: + * Docid limit and serial number are used to complete the prepared reconfig. + * This is done by the DocumentDB master write thread. * - * Apply: - * The new components are swapped with the old ones in the DocumentDB master write thread. + * 3) Apply: + * The new components are swapped with the old ones. + * This is done by the DocumentDB master write thread. */ class DocumentDBReconfig { private: |