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.