From d1e95134d8af7e4a0ea49ee03d4bb1878ecdc981 Mon Sep 17 00:00:00 2001
From: Samuel Just <samuel.just@dreamhost.com>
Date: Tue, 1 Nov 2011 11:16:53 -0700
Subject: [PATCH] PG: set_last_peering_reset in Reset constructor

If an osd in the prior set comes up, we can restart peering without a
new peering interval starting.  However, we still want to ignore
anything we previously requested from replicas.

Signed-off-by: Samuel Just <samuel.just@dreamhost.com>
---
 src/osd/PG.cc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/osd/PG.cc b/src/osd/PG.cc
index 7621f7ca063c2..d6ede4cc60282 100644
--- a/src/osd/PG.cc
+++ b/src/osd/PG.cc
@@ -3911,6 +3911,8 @@ void PG::RecoveryState::Started::exit() {
 PG::RecoveryState::Reset::Reset(my_context ctx) : my_base(ctx) {
   state_name = "Reset";
   context< RecoveryMachine >().log_enter(state_name);
+  PG *pg = context< RecoveryMachine >().pg;
+  pg->set_last_peering_reset();
 }
 
 boost::statechart::result 
-- 
2.39.5