tree baa81813f32de8939a09bc4c35fc5ed092f006b9
parent 7fc542ed2590942edf757dfcc34a8a9aa926a258
author Han-Wen Nienhuys <hanwen@google.com> 1497973026 +0200
committer Han-Wen Nienhuys <hanwen@google.com> 1497973446 +0200

Revert "Load shards as fast as we can"

The current strategy has an unexplained deadlock, which apparently
triggers when read requests happen concurrently with reloads.

Since the GCP load balancer issues a continuing stream of HTTP
requests for /, each of which triggers a read across shards, the
deadlock trigger in production reliably.

This reverts commit e9c19a019ce90ce9ce7021c81c8d0bb10aedeaed.

Change-Id: I5b5234d204a9e9303ab84b098443dd9e9709318f