Sets the maximum degree of parallelism (in effect the maximum number of
client-side threads) to be used when running a parallel store iteration.
Setting maxConcurrentRequests to 1 causes the store iteration to be
performed using only the current thread. Setting it to 0 lets the KV
Client determine the number of threads based on topology information (up
to a maximum of the number of available processors as returned by
java.lang.Runtime.availableProcessors()). Values less than 0 are
reserved for some future use and cause an IllegalArgumentException to be
maxConcurrentRequests - the maximum number of client-side threads.
Specifies the maximum number of results batches that can be held in the
NoSQL Database client process before processing on the Replication Node
pauses. This ensures that client side memory is not exceeded if the
client can't consume results as fast as they are generated by the Rep
Nodes. The default value is the value of maxConcurrentRequests.
maxResultsBatches - the maximum number of results sets that can be
held on the client side before Replication Node processing pauses.