summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSage Weil <sage@inktank.com>2013-07-05 16:03:49 -0700
committerSage Weil <sage@inktank.com>2013-07-08 09:33:14 -0700
commita02f2510fcc800b9f2cf2a06401a7b97d5985409 (patch)
treee982efb11be8782027af24973f8de7a27114dcf7
parentdb2bb270e93ed44f9252d65d1d4c9b36875d0ea5 (diff)
downloadceph-a02f2510fcc800b9f2cf2a06401a7b97d5985409.tar.gz
mon: remove bad assert about monmap version
It is possible to start a sync when our newest monmap is 0. Usually we see e0 from probe, but that isn't always published as part of the very first paxos transaction due to the way PaxosService::_active generates it's first initial commit. In any case, having e0 here is harmless. Fixes: #5509 Signed-off-by: Sage Weil <sage@inktank.com> Reviewed-by: Joao Eduardo Luis <joao.luis@inktank.com> (cherry picked from commit 85a1d6cc5d3852c94d1287b566656c5b5024fa13)
-rw-r--r--src/mon/Monitor.cc1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/mon/Monitor.cc b/src/mon/Monitor.cc
index 42fc15c5905..9d436f1e569 100644
--- a/src/mon/Monitor.cc
+++ b/src/mon/Monitor.cc
@@ -1384,7 +1384,6 @@ void Monitor::sync_obtain_latest_monmap(bufferlist &bl)
if (monmap->epoch > latest_monmap.epoch)
latest_monmap = *monmap;
- assert(latest_monmap.epoch > 0);
dout(1) << __func__ << " obtained monmap e" << latest_monmap.epoch << dendl;
latest_monmap.encode(bl, CEPH_FEATURES_ALL);