Actions
Bug #16326
closed[doc] improve MaxConcurrentRequests and MaxKeepBlobBuffers descriptions
Story points:
-
Release:
Release relationship:
Auto
Description
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.
Updated by Ward Vandewege over 4 years ago
- Status changed from New to In Progress
Updated by Ward Vandewege over 4 years ago
Developer tests running at developer-run-tests: #1805 . Ready for review at b0205e1c5e8bff315b475c6a2122bb23fbead70c on branch 16326-doc-and-keepstore-update
Updated by Ward Vandewege over 4 years ago
- Release changed from 25 to 30
- Status changed from In Progress to Resolved
Merged to master.
Actions