{"push_id":2317412110,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e0b8d5f35710de8cb3fab19b3b62165d13c1a504","before":"99db8cac7b312b7963fd83f03ef1beaf5a626a77","commits":[{"sha":"e0b8d5f35710de8cb3fab19b3b62165d13c1a504","author":{"name":"Mitch Rudominer","email":"881e2d82bed21e5676a4717e7d9f18e0a34d9d06@google.com"},"message":"Adds retries to Bigtable Reads.\n\nPreviously we used retry logic for Bigtable writes but not for Bigtable reads.\nThis CL implements retry logic for reads too.\n\nThis is important as it appears to be a common pattern that the first RPC\nto Bigtable after the connection has gotten \"cold\" somehow always returns\na transient failure. In my experimentation this retry logic always succeeds\nafter one retry.\n\nThe symptom I noticed that I am trying to fix is that the ReportScheduler will\nfrequently skip running a report because it fails to read the metadata for\nthat report and so it cannot determine if there is already an instance\nof the report running. I have observed that this fixes that problem.\n\nChange-Id: I038f31eda7471434bebd2ad21a4fdc9aede529f9","distinct":true,"url":"https://api.github.com/repos/fuchsia-mirror/cobalt/commits/e0b8d5f35710de8cb3fab19b3b62165d13c1a504"}]}
{"actor":{"display_login":"FF0080"}}