dbft: do not send PrepareRequest immediately after Recovery message

We have timer, and we should follow it. Close #74.

Signed-off-by: Anna Shaleva <anna@nspcc.ru>

dbft.go

@@ -294,7 +294,7 @@ func (d *DBFT) start() {
 func (d *DBFT) onPrepareRequest(msg payload.ConsensusPayload) {
 	// ignore prepareRequest if we had already received it or
 	// are in process of changing view
-	if d.RequestSentOrReceived() { //|| (d.ViewChanging() && !d.MoreThanFNodesCommittedOrLost()) {
+	if d.RequestSentOrReceived() { // || (d.ViewChanging() && !d.MoreThanFNodesCommittedOrLost()) {
 		d.Logger.Debug("ignoring PrepareRequest due to view changing",
 			zap.Bool("sor", d.RequestSentOrReceived()),
 			zap.Bool("viewChanging", d.ViewChanging()),
@@ -593,9 +593,9 @@ func (d *DBFT) onRecoveryMessage(msg payload.ConsensusPayload) {
 			if prepReq != nil {
 				totalPrepReq, validPrepReq = 1, 1
 				d.OnReceive(prepReq)
-			} else if d.IsPrimary() {
-				d.sendPrepareRequest()
 			}
+			// If the node is primary, then wait until timer fires to send PrepareRequest
+			// to avoid rush in blocks submission, #74.
 		}
 
 		for _, m := range recovery.GetPrepareResponses(msg, d.Validators) {