Repair for partial data loss in a database aware distributed data store

Abstract

For database high availability without data loss, a storage drive is resilvered in the background while all replicas of a database remain in service. A distributed system persists a first replica of a database in a first storage computer (SC) and a second replica of the database in a second SC. The database contains a database extent that contains a database block. An instance of the database block is persisted in a storage drive of the first SC. When data loss of the database block instance is discovered, the first SC increments a repair count of the database. While the first SC repairs the damaged database extent that includes the lost database block, a second SC detects that the repair count of the database exceeds a repair count in a write request, which causes the write request to be rejected in a way that indicates that the write request should be retried.

Dependencies are inferred from the claim text.