Ed Hennis dd5e6559dd Reduce duplicate peer traffic for ledger data (#5126) ...

- Drop duplicate outgoing TMGetLedger messages per peer
  - Allow a retry after 30s in case of peer or network congestion.
  - Addresses RIPD-1870
  - (Changes levelization. That is not desirable, and will need to be fixed.)
- Drop duplicate incoming TMGetLedger messages per peer
  - Allow a retry after 15s in case of peer or network congestion.
  - The requestCookie is ignored when computing the hash, thus increasing
    the chances of detecting duplicate messages.
  - With duplicate messages, keep track of the different requestCookies
    (or lack of cookie). When work is finally done for a given request,
    send the response to all the peers that are waiting on the request,
    sending one message per peer, including all the cookies and
    a "directResponse" flag indicating the data is intended for the
    sender, too.
  - Addresses RIPD-1871
- Drop duplicate incoming TMLedgerData messages
  - Addresses RIPD-1869
- Improve logging related to ledger acquisition
- Class "CanProcess" to keep track of processing of distinct items

---------

Co-authored-by: Valentin Balaschenko <13349202+vlntb@users.noreply.github.com>

2025-02-14 18:51:51 -05:00

..

basics

Reduce duplicate peer traffic for ledger data (#5126)

2025-02-14 18:51:51 -05:00

beast

Antithesis instrumentation improvements (#5213)

2024-12-16 17:48:33 -05:00

crypto

Rearrange sources (#4997)

2024-06-20 13:57:14 -05:00

json

Add Antithesis intrumentation (#5042)

2024-12-03 14:54:44 -05:00

proto

Reduce duplicate peer traffic for ledger data (#5126)

2025-02-14 18:51:51 -05:00

protocol

Reduce duplicate peer traffic for ledger data (#5126)

2025-02-14 18:51:51 -05:00

resource

fix: Replace charge() by fee_.update() in OnMessage functions (#5269)

2025-02-13 08:54:01 -08:00

server

Fix CI unit tests (#5196)

2025-01-28 10:45:59 -05:00