History Start Seqno obtained from Cbstats does not match the value obtained from Magma

Data from nodes has been copied to the folder /vibhav in node 172.23.106.120

Username: root, password:couchbase
Steps:

1. Initialise a 3 node cluster running just the KV service.
2. Create a Magma bucket with 2 replicas and 256MB RAM per node.
3. Load 100,000 items into every collection. The bucket has 6 collections.
4. After initial inserts, update all the 100,000 items in the collection. This step is performed 4 times iteratively. So, in total, we update the items 4 times.
5. Restart Couchbase server on all the nodes and wait for 60 seconds before validation.
6. Validation includes fetching sequence number count from magma_dump. 

   /opt/couchbase/bin/magma_dump /data/default/magma.0 docs --index seq --kvstore 192 --history | wc -l

   The above magma_dump command is run to fetch all the copies of documents from history.

1. Running this command tells us that the history start sequence number is changed.

/opt/couchbase/bin/magma_dump /data/default/magma.0 history-seqno --kvstore 152 

{

    "historyEnabledSeqno": 1,

    "historySeqno": 1331

} 

# Cbstats reports that the history start sequence number is still 1 for all vbuckets.

1. Cb-collect logs have been attached.