Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Cheshire-Cat
-
Untriaged
-
1
-
Unknown
Description
1. avoid restarting ns_server during upgrade to chronicle, Per comments here: http://review.couchbase.org/c/ns_server/+/138203
2. make sure that we can recover after aborted upgrade
3. reset all caches that rely on chronicle events after the upgrade to chronicle
To avoid this potential scenario:
- a. Key is upgraded to chronicle
- b. Key changed in chronicle
- c. Cache refreshes, but from ns_config since the compat version is not changed yet
- d. compat version changes to chronicle, but the change made in #2 is not cached
4. make sure that no chronicle_kv events lost during the upgrade, Per comments here: http://review.couchbase.org/c/ns_server/+/134593