daos
daos copied to clipboard
DAOS-9206 dfs: add container hints for better object class selection
DAOS object class selection today is either done explicitly by the user or otherwise automatically depending on the type of the object. However this has proven to be still not sufficient from a user perspective as there is not control on the sharding with automatic selection. For example:
- EC is automatically chosen for files / arrays, but would be be bad for small files vs replication
- S1 or G1 is chosen for directories, but for fat directories, SX/GX is better
This PR adds some flags to POSIX containers passed at creation time:
- dir_oclass (to set explicit oclass for directories to distinguish from files)
- hints: tiny/small/medium/large_file/dir to help DAOS better choose an object class for files or directories
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/1/execution/node/131/log
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/2/execution/node/133/log
Test stage Unit Test completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/3/execution/node/736/log
Bug-tracker data: Ticket title is 'New POSIX container options (hints) for default object classes' Status is 'Open' Labels: 'triaged' Job should run at elevated priority (3) https://daosio.atlassian.net/browse/DAOS-9206
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/12/execution/node/174/log
Do you want functional test coverage for the hints and/or dir obj class?
i have added DFS tests for the hints. the dir oclass probably need to add some nlt tests. i will do that in a follow on PR.
Do you want functional test coverage for the hints and/or dir obj class?
i have added DFS tests for the hints. the dir oclass probably need to add some nlt tests. i will do that in a follow on PR.
Sure. Let me know if you want help with any ftest additions
-1 because of the doxygen warning, if this is landed as-is then all builds will fail with that warning until fixed.
where is the doxygen warning? the PR is green so how will PRs fail?
Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-9375/19/testReport/(root)/
refreshed with README update (no code changes)
Test stage Python Bandit check completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/20/execution/node/144/log
Test stage Python Bandit check completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/21/execution/node/143/log
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/21/execution/node/1186/log
-1 because of the doxygen warning, if this is landed as-is then all builds will fail with that warning until fixed.
your comments have been addressed, can you please review again?
rebase to resolve conflict
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9375/22/execution/node/1169/log
failed test is unrelated and tracked here: https://daosio.atlassian.net/browse/DAOS-11749