[doc] improve MaxConcurrentRequests and MaxKeepBlobBuffers descriptions
The detail on how to calculate MaxKeepBlobBuffers was accidentally dropped in the 2.0 doc update.
The description for MaxConcurrentRequests erroneously states that it is only used by Keepstore.
The description for MaxConcurrentRequests states that the default (0) means no limit, but in the Keepstore code, 0 is translated to 2 * MaxKeepBlobBuffers.
documentation: update descriptions for MaxKeepBlobBuffers and MaxConcurrentRequests
keepstore: MaxConcurrentRequests set to zero should mean no limit
keepstore: warn if MaxConcurrentRequests is set to a nonzero value less
Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <email@example.com>
#3 Updated by Ward Vandewege over 1 year ago
Developer tests running at https://ci.arvados.org/view/Developer/job/developer-run-tests/1805/. Ready for review at b0205e1c5e8bff315b475c6a2122bb23fbead70c on branch 16326-doc-and-keepstore-update