Retransmit container related commands to other storage nodes #426

New issue

Open

opened 2025-12-28 17:19:26 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:19:26 +00:00

Owner

Originally created by @alexvanin on GitHub (Jan 27, 2022).

If the Storage node configured in relay mode, then it may not have any side chain GAS on it's account. And even if it has side chain GAS, it won't be updated during side chain GAS emission, because GAS goes to the Storage nodes from network map.

Without side chain GAS, storage node can't process container related operation, because they trigger chain invocations.
To solve this issue, storage node may find nodes from the network map and resend request to the nearest node.

Originally created by @alexvanin on GitHub (Jan 27, 2022). If the Storage node configured in relay mode, then it may not have any side chain GAS on it's account. And even if it has side chain GAS, it won't be updated during side chain GAS emission, because GAS goes to the Storage nodes from network map. Without side chain GAS, storage node can't process container related operation, because they trigger chain invocations. To solve this issue, storage node may find nodes from the network map and resend request to the nearest node.

sami added the

neofs-storage

feature

labels

2025-12-28 17:19:26 +00:00

sami commented

2025-12-28 17:19:26 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (May 12, 2022):

Solution

In each Container service handler, if node is configured with relay flag, do:

recv network map
select "closest" node from the netmap (in initial implementation it could be a random node)
forward request to the selected node and forward response from it

@cthulhu-rider commented on GitHub (May 12, 2022): ## Solution In each `Container` service handler, if node is configured with `relay` flag, do: 1. recv network map 2. select "closest" node from the netmap (in initial implementation it could be a random node) 3. forward request to the selected node and forward response from it