diff options
author | Kristian Aune <kkraune@users.noreply.github.com> | 2020-11-30 11:22:11 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-11-30 11:22:11 +0100 |
commit | 8507d71d227bd39dbe605bfc3ce099b039fedebb (patch) | |
tree | 0f0afc3fbad2362e9d2912b0702dc80a0390dc71 /ERRATA.md | |
parent | ed01d175b7201f5d8047b82ec33387fcbdbe8cbf (diff) | |
parent | bf493134bc7e1b28bf7f1e84a53f44e01d3ab83a (diff) |
Merge pull request #15529 from vespa-engine/kkraune/errata
first cut errata
Diffstat (limited to 'ERRATA.md')
-rw-r--r-- | ERRATA.md | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/ERRATA.md b/ERRATA.md new file mode 100644 index 00000000000..97636826c36 --- /dev/null +++ b/ERRATA.md @@ -0,0 +1,38 @@ +<!-- Copyright verizon Media. Licensed under the terms of the Apache 2.0 license. See LICENSE in the project root. --> + +## Errata + +### 2020-11-30: Document inconsistency +This bug was introduced in Vespa-7.277.38, fixed in Vespa-7.292.82. +The following needs to happen to trigger the bug: + +* visibility-delay is non-zero. Note that the default is zero, so for this to trigger, + [https://docs.vespa.ai/documentation/reference/services-content.html#visibility-delay](visibility-delay) + must have been set. +* A new config change is deployed that contains changes to proton. + This config snapshot is stored in the transaction log on the content node. +* vespa-proton-bin is restarted, and as part of the prepare for restart step, + at least one attribute vector is not flushed to the current serial number. +* Due to the bug, replay of the transaction log will fail to replay feed operations to attributes after replaying the config change. + The effect is that all attributes that were not flushed as part of prepare for restart + will not get any of the updates since the last time they were flushed. +* If a document was previously removed, lid space compaction will move another document to that local document id. + Due to later missing updates as part of restarting we might see values from the removed document for some of the attributes. +* When the problem attributes are later flushed this inconsistency will be permanent. + +Solution: +* Upgrade Vespa to minimum Vespa-7.292.82. +* Complete re-feed of the corpus. + + + +### 2020-11-30: Regression introduced in Vespa 7.141 may cause data loss or inconsistencies when using 'create: true' updates +There exists a regression introduced in Vespa 7.141 where updates marked as `create: true` (i.e. create if missing) +may cause data loss or undetected inconsistencies in certain edge cases. +This regression was introduced as part of an optimization effort to greatly reduce the common-case overhead of updates +when replicas are out of sync. + +Fixed in Vespa 7.157.9 and beyond. +If running a version affected (7.141 up to and including 7.147) you are strongly advised to upgrade. + +See [#11686](https://github.com/vespa-engine/vespa/issues/11686) for details. |