When doing a bucket flush only send reset to mccouch once

Since we have multiple shards in that each have a kvstore we should
only allow one of the shards to send a flush notification to
mccouch.

Change-Id: I62a4fe0b954f5a004f1c16bfbdb57b7fabfa04c8
Reviewed-on: http://review.couchbase.org/32796
Reviewed-by: Chiyoung Seo <chiyoung@couchbase.com>
Tested-by: Michael Wiederhold <mike@couchbase.com>
Only create vb0 if neccesary after warmup

Since warmup will initialize a vbucket based on it's past state we
should only create the default vbucket 0 if one is not loaded
during warmup.

Note that the changes in checkpoint numbers for the tests are
needed because we are actually creating vbucket 0 properly and
that means for an active vbucket starting the open checkpoint
at 1 instead of 0.

Change-Id: I35b7d8a3b94d7292a1116496f901fb5a48634044
Reviewed-on: http://review.couchbase.org/32780
Reviewed-by: Michael Wiederhold <mike@couchbase.com>
Tested-by: Michael Wiederhold <mike@couchbase.com>
Dont allow copying of the FailoverTable

This will prevent us from having to copy the failover log class
in different places. We generally do not allow classes to be copied.

Change-Id: I4d4fafbe90501006963c8ba201f6dc7ebf2e464e
Reviewed-on: http://review.couchbase.org/32821
Reviewed-by: Michael Wiederhold <mike@couchbase.com>
Tested-by: Michael Wiederhold <mike@couchbase.com>
Refactor the failover log

This change should make things simpler and also adds some
documentation to the failover log header file.

Change-Id: I0b69465f56efb604f97cccf3692217302420d380
Upr consumer should persist failover log on stream creation

Change-Id: I79fb5494c649e8bec5a1a0665b6c2545017cd256
Parallelize creation of vbuckets during warmup

Right now we create all vbuckets during warmup from the same
thread. We also call the initVBuckets function multiple times
during wamrup and although we will only create the vbuckets once
calling this function over and over again is unnecessary. This
change introduces a new warmup state for creating vbuckets.

Change-Id: If0b49d618408f646492168c39a59d7aa34b07b50
Don't create a failover entry after a clean shutdown

We are only required to create new failover entries after a crash
so we should check to see if that happened before creating one
during warmup.

Change-Id: I128eceaca719f6e44e683e17223445a8b328cad5
MB-9892: Add correct vb uuid and high seqno to consumer stream req

Change-Id: I7d26fc7a55b4e86f85603b99e26c9d1c3dac6246
Make sure all ConnHandlers have a Connection object

This will allow us to be able to set the logHeader() function to
allow us to better categorize upr and tap log messages.

Change-Id: Ib61cc3f388fc536d5a4f6739e89bca7a286a200d
Add more upr info log messages for better debugging

Change-Id: I21a802b8f041376c1df6b138173c0053b15e0843
Make sure upr mutation/deletion messages by_seqno's increase

Change-Id: I6837d68fdfc798c5e4203080f271c62137acaaf4
Close a stream if the vbucket state changes

Change-Id: Ib17f813e7249e9ae85ed8166e0269cf7a48789c7