Fetching strategy if object is not found locally #1216

New issue

Open

opened 2025-12-28 17:22:13 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:22:13 +00:00

Owner

Originally created by @carpawell on GitHub (Apr 27, 2024).

I'm always frustrated when I know that a node responds with the first API (error) status it gets from another node even if there is more nodes to try.

Describe the solution you'd like

Try to get some meaningful number of the same responses and only then answers with it (REP number? 2/3+1 number?).

Describe alternatives you've considered

Complex statuses and the other things from the https://github.com/nspcc-dev/neofs-node/issues/1709#issuecomment-2044490058.

Additional context

https://github.com/nspcc-dev/neofs-node/issues/1709, https://github.com/nspcc-dev/neofs-node/pull/2836 (PR that makes local response priority).

Originally created by @carpawell on GitHub (Apr 27, 2024). ## Is your feature request related to a problem? Please describe. I'm always frustrated when I know that a node responds with the first API (error) status it gets from another node even if there is more nodes to try. ## Describe the solution you'd like Try to get some meaningful number of the same responses and only then answers with it (REP number? 2/3+1 number?). ## Describe alternatives you've considered Complex statuses and the other things from the https://github.com/nspcc-dev/neofs-node/issues/1709#issuecomment-2044490058. ## Additional context https://github.com/nspcc-dev/neofs-node/issues/1709, https://github.com/nspcc-dev/neofs-node/pull/2836 (PR that makes local response priority).