Bug #22184
Updated by Tom Clegg 5 months ago
Originally this was a flaky test bug report: * keep-web IntegrationSuite.TestConcurrentWrites fails intermittently * at At commit:9cb3284ca1, ran the test 100x, got 4x failures. The underlying problem was that (since #21702) keep-web's cache behaves eventually-consistent in a way that is likely to confuse clients (e.g., if a client reads a file soon after updating/replacing that file with new content, the old content might be returned). Before #21702, this problem only existed in a load-balanced setup -- as long as there was only one keep-web process, writes to a given collection ID were serialized and the cached filesystem was updated after each write, so no request used an outdated view of a collection. This issue now aims to fix the problem even for load-balanced setups.