DAOS-19116 object: drop reference when fail in obj_ioc_begin_lite - b28#18705
DAOS-19116 object: drop reference when fail in obj_ioc_begin_lite - b28#18705Nasf-Fan wants to merge 1 commit into
Conversation
|
Ticket title is 'daos_racer/simple.py:DaosRacerSimpleTest.test_daos_racer_simple - Error running 'daos_racer'; timed out daos_racer process' |
|
Test stage Build on EL 9 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-18705/1/execution/node/534/log |
|
Test stage Build on EL 8 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-18705/1/execution/node/582/log |
|
Test stage Build on Leap 15 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-18705/1/execution/node/628/log |
ca40099 to
1e6d229
Compare
It is possible that obj_ioc_begin_lite() maybe failed because of empty or stale pool map on server. At that time, the logic has already held reference against the container open handle. Under such case, directly returning error# to the caller may cause reference leak as to such container cannot be properly stopped in subsequent operations. Signed-off-by: Fan Yong <fan.yong@hpe.com>
1e6d229 to
fc838f2
Compare
It is possible that obj_ioc_begin_lite() maybe failed because of empty or stale pool map on server. At that time, the logic has already held reference against the container open handle. Under such case, directly returning error# to the caller may cause reference leak as to such container cannot be properly stopped in subsequent operations.
Steps for the author:
After all prior steps are complete: