tree ea931b660df136bc5c1d8a38d2bbcb20796b1c1d
parent c31dff9ff8dc3ec7454a62d71a9fff2af8505ee9
author Jack Vanlightly <vanlightly@gmail.com> 1659337895 +0200
committer GitHub <noreply@github.com> 1659337895 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi53ynCRBK7hj4Ov3rIwAAcBMIADajj0ed7SVMiXQXDXPuBG2U
 fXRIDEymcWW3Z3JgEW9iHjWl/1Vn7LpS+8T+VsokTk9VDgdesFoZlNL3NGlt9N8U
 2akFxGPXUh36GnmN/Af18ec8F+rETqOGfBRuxusC1tzs4dT11YdCO/Mwl7eY31i0
 5TpbG86SEvVsWVJjBycIjvhLeqlwVrR9ahl7q6oFPoGETgDyzaWmpWsJEhwdGVTn
 /B31nWjWekiStNfZ7aU9xRlV/WJArLcyxtNIvUhLxy+zL55zOvYfV86vktI+fB8c
 OoaSerCxvsl6x6cvGAnCxqn0FNLhOibv4hpqOd8hOtaVSRdZutrVtOIlb/b9NMo=
 =gJz6
 -----END PGP SIGNATURE-----
 

Issue #2908: Replace unsafe NoEntryException with IOException (#2909)

* Replace unsafe NoEntryException with IOException

Throwing a NoEntryException from the entry logger
for an entry that the index says should exist is
unsafe. It can cause ledger truncation during ledger
recovery. It only takes a single false NoSuchEntry
response to trigger truncation.

NoEntryException should only be thrown from inside
ledger storage if the entry is not found in the index.

* fix CI

Co-authored-by: chenhang <chenhang@apache.org>