retry mechanism for read operations

[0xluk]

Why? Who?

As a read endpoint triggers a core node request to only one node, if the node connection drops or if the request fails due to a server(core node) error the system also returns the error.

Acceptance criteria

Each read request needs to retry x times(TBD) to be able to return a proper response to the client.

References

Error in request to: https://rpc.qubic.org/v1/tick-info
Error Body: {code: 13, message: getting tick info from node sending req to node: reading response for req type 27: unmarshalling response: reading header: read tcp 172.19.0.10:53780->5.39.222.65:21841: read: connection reset by peer, details: []}