Major Description
Problem
cbbackupmgr has it's only gentator which is used for:
1. Testing the frontend of cbbackupmgr without needing disks
2. For ease of loading data into a cluster.
For point 2 loading a large amount of data into a cluster can be very time comsuing. The quickest way would be to have a data generator on each data node that loads only the active vBuckets on that node. As all the traffice would be going over loop back.
Requests
It would be great if the genertor in cbbackupmgr had a new argument like -local/single-node where it only populates the vBuckets that is local to the node it's being executed on. For example on a 3 node cluster you would run the same commad on each node:
cbbackupmgr -n 1000000 -b beer-sample --local -c localhost -u Administor -p password
|
In total a 1m docs would be loaded but each cbbackupmgr would only load rough a thrid of the data.