-
Notifications
You must be signed in to change notification settings - Fork 142
CORTX-33537: allow degraded i/o for the new objects #1959
Conversation
42de7ea
to
d304d64
Compare
d97232f
to
12f0856
Compare
12f0856
to
7881087
Compare
This comment was marked as outdated.
This comment was marked as outdated.
@andriytk: Following ut seems to be stuck, which seems to be related to this PR only. |
Currently, if no clean pool version (actual or formulaic) can be found for the new object on its creation, -ENOENT is returned, which is not good. We want the user to be able to create new objects even if this implies the degraded i/o on them. Solution: return the actual pver at conf_pver_find_locked() in case when nothing better (cleaner) can be found. Closes Seagate#1958. Relates Seagate/cortx-hare#2123. Signed-off-by: Andriy Tkachuk <andriy.tkachuk@seagate.com>
7881087
to
7c2b423
Compare
Jenkins CI Result : Motr#1438Motr Test Summary
CppCheck SummaryCppcheck: No new warnings found 👍 |
Seems known and not caused by this patch. Right, @madhavemuri, @huanghua78 ? |
This will be fixed in #1951 |
retest this please |
Currently, if no clean pool version (actual or formulaic)
can be found for the new object on its creation, -ENOENT is
returned, which is not good. We want the user to be able to
create new objects, even if this implies the degraded i/o on
them.
Solution: return the actual pver at conf_pver_find_locked()
in case when nothing better (cleaner) can be found.
Closes #1958.
Relates Seagate/cortx-hare#2123.
Coding
Checklist for Author
Testing
Checklist for Author
Impact Analysis
Checklist for Author/Reviewer/GateKeeper
Review Checklist
Checklist for Author
Documentation
Checklist for Author