Fix read records

[yito88]

Description

Try to read each account with retries.
Basically, the backoff retry is to wait for the DB bootstrapping after the nemesis, not to recover these records. When some records needed to be recovered, e.g. all 10 records, the test failed because the retry count (8) was fixed.

Related issues and/or PRs

Changes made

• Make read-all to read each account with retries.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

[komamitsu]

LGTM! 👍

[feeblefakie]

LGTM! Thank you!

[brfrn169]

Left a minor comment. Other than that, LGTM! Thank you!

[brfrn169]

I think we can catch CrudConflictException if it's for the lazy recovery. What do you think?

[yito88]

@brfrn169 Another exception could be thrown from the commit, couldn't it?

[brfrn169]

@yito88 Sorry, it seems I had the wrong idea. Please ignore the comment.

So currently, we retry all the record reads together, but after this PR, we will retry each record read individually. Is my understanding correct?

[yito88]

@brfrn169 No problem. "read-record" tries to update, so it's a bit misleading.

we retry all the record reads together, but after this PR, we will retry each record read individually. Is my understanding correct?

Exactly!

[brfrn169]

Thanks!