Details
-
Bug
-
Resolution: Fixed
-
Critical
-
2.1.0
-
None
-
Security Level: Public
-
None
Description
max_num_shards doesn't correctly represent the value a user set up via UI. It is really an approximate total number of data access threads the user wanted to deploy per bucket.
Thus change this parameter name to max_num_workers and add / modify workload codes so num_shards will be internally calculated based on num_workers.
Attachments
| For Gerrit Dashboard: MB-8415 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 26772,11 | MB-8415 change num_shards parameter to num_workers | 2.1.0 | ep-engine | Status: MERGED | +2 | +1 |
| 26776,2 | MB-8415 change engine parameter num_shards to num_workers | 2.1.0 | ns_server | Status: MERGED | +2 | +1 |
| 26786,2 | Revert "MB-8415 change engine parameter num_shards to num_workers" | 2.1.0 | ns_server | Status: MERGED | +2 | +1 |
| 26787,3 | Revert "Revert "MB-8415 change engine..."" | 2.1.0 | ns_server | Status: MERGED | +2 | +1 |
| 26796,4 | MB-8415 set minum num_threads back to 2 and set default to 3 | 2.1.0 | ns_server | Status: MERGED | +2 | +1 |
| 26807,1 | Merge remote-tracking branch 'origin/2.1.0' | master | ns_server | Status: MERGED | +2 | +1 |
| 26854,1 | Merge remote-tracking branch 'origin/2.1.0' | master | ns_server | Status: MERGED | +2 | +1 |