RPC ConsistencyCheck and Praefect "reconcile" subcommand

1 files changed, 30 insertions, 0 deletions

diff --git a/proto/praefect.proto b/proto/praefect.proto
index f51d8f5b6..80312b554 100644
--- a/proto/praefect.proto
+++ b/proto/praefect.proto
@@ -14,6 +14,16 @@ service PraefectInfoService {
       scope_level: SERVER
     };
   }
+  // ConsistencyCheck will perform a consistency check on the requested
+  // virtual storage backend. A stream of repository statuses will be sent
+  // back indicating which repos are consistent with the primary and which ones
+  // need repair.
+  rpc ConsistencyCheck(ConsistencyCheckRequest) returns (stream ConsistencyCheckResponse) {
+    option (op_type) = {
+      op: ACCESSOR
+      scope_level: STORAGE
+    };
+  }
 }
 
 message RepositoryReplicasRequest{
@@ -29,3 +39,23 @@ message RepositoryReplicasResponse{
   RepositoryDetails primary = 1;
   repeated RepositoryDetails replicas = 2;
 }
+
+message ConsistencyCheckRequest {
+  string virtual_storage = 1 [(storage)=true];
+  // The target storage is the storage you wish to check for inconsistencies
+  // against a reference storage (typically the current primary).
+  string target_storage = 2;
+  // Optionally provide a reference storage to compare the target storage
+  // against. If a reference storage is omitted, the current primary will be
+  // used.
+  string reference_storage = 3; 
+}
+
+message ConsistencyCheckResponse {
+  string repo_relative_path = 1;
+  string target_checksum = 2;
+  string reference_checksum = 3;
+  // If resync was enabled, then each inconsistency will schedule a replication
+  // job. A replication ID is returned to track the corresponding job.
+  uint64 repl_job_id = 4;
+}