Consistent Fallback Shard Assignments Accessor
Notes: Shard assignment rollout - replica rollout strategy does not work well with current worker child resilient strategy - maybe another rollout strategy - shard poisoning check - only done when result get from replica - AI: if the underlying connection is replica, we probably need to do shard poisoning too. - update 12-10-22: don’t need to do the shard poisoning check, because we will not commit a crud request transaction against a stale replica. - TODO: think about the name of a new accessor that makes it clear that we expect to re-run queries against the replica - Also need to annotate
uid: 202211281340 tags: #airtable