summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoao Eduardo Luis <jecluis@gmail.com>2013-08-28 17:42:14 +0100
committerJoao Eduardo Luis <jecluis@gmail.com>2013-08-29 00:48:20 +0100
commit274b4b96cfaf46a465081880ace0bad5bd8da12d (patch)
tree8bdc27e8da6be02b2e2476d1f8eccb63d155b149
parentfab79543c54c2e446d3f76520d7906645c6b0075 (diff)
downloadceph-274b4b96cfaf46a465081880ace0bad5bd8da12d.tar.gz
mon: OSDMonitor: don't propose on prepare_pool_op()
Except in very special cases, we should let PaxosService take its course and trigger the proposals itself. In this case, we were proposing right before returning to PaxosService, and we were returning false on top of it (most likely to guarantee that PaxosService wouldn't try to propose). This doesn't make much sense, so let's do it like all the other cool kids are doing and let PaxosService decide what's best for us. Signed-off-by: Joao Eduardo Luis <jecluis@gmail.com>
-rw-r--r--src/mon/OSDMonitor.cc3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/mon/OSDMonitor.cc b/src/mon/OSDMonitor.cc
index 9fcc0912550..f56982bc737 100644
--- a/src/mon/OSDMonitor.cc
+++ b/src/mon/OSDMonitor.cc
@@ -3879,8 +3879,7 @@ bool OSDMonitor::prepare_pool_op(MPoolOp *m)
out:
wait_for_finished_proposal(new OSDMonitor::C_PoolOp(this, m, ret, pending_inc.epoch, &reply_data));
- propose_pending();
- return false;
+ return true;
}
bool OSDMonitor::prepare_pool_op_create(MPoolOp *m)