Fix the "Log Matching Property check failed" message
Fix the "Log Matching Property check failed" message

Right now you get this message after tablets are created:
I1020 16:21:19.065383 27694 consensus_queue.cc:315] Peer: ad95373a915c435f99be6d1e681d7c77 replied
that the Log Matching Property check failed. Queue's last received watermark for peer: NONE.
Peer's actual last received watermark: term: 0 index: 0

Which is a pretty scary message at INFO level, and it's actually something normal. This patch
changes the normal case to print a nice message saying that we connected to the peer, and the above
will now be at WARNING.

Change-Id: I0e35963ea8cf5507bf6a9aaceec51d0b23cd1d8e
Reviewed-on: http://gerrit.sjc.cloudera.com:8080/4903
Tested-by: jenkins
Reviewed-by: Todd Lipcon <2c763d726a8c2f6afda9be7e0e56a2caa6bb5e6b@cloudera.com>

andrwng/kudu,InspurUSA/kudu,cloudera/kudu,InspurUSA/kudu,InspurUSA/kudu,helifu/kudu,helifu/kudu,InspurUSA/kudu,EvilMcJerkface/kudu,helifu/kudu,EvilMcJerkface/kudu,andrwng/kudu,cloudera/kudu,InspurUSA/kudu,InspurUSA/kudu,cloudera/kudu,helifu/kudu,andrwng/kudu,andrwng/kudu,EvilMcJerkface/kudu,andrwng/kudu,helifu/kudu,cloudera/kudu,helifu/kudu,helifu/kudu,InspurUSA/kudu,andrwng/kudu,EvilMcJerkface/kudu,cloudera/kudu,EvilMcJerkface/kudu,helifu/kudu,andrwng/kudu,EvilMcJerkface/kudu,EvilMcJerkface/kudu,andrwng/kudu,InspurUSA/kudu,cloudera/kudu,InspurUSA/kudu,helifu/kudu,EvilMcJerkface/kudu,EvilMcJerkface/kudu,andrwng/kudu,cloudera/kudu,cloudera/kudu,cloudera/kudu