nspcc-dev / nspcc-dev/neofs-node

Consider using `--await` in `control set-status`

Open
#1,790 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion I3 neofs-cli S4 U3
Dominant language
Go
Stars
38
Forks
51
Avg merge
1d 20h
Merged PRs (30d)
38

Description

In many neofs-cli commands we have --await flag for waiting until completion.
It would be nice to use it with set-status to be sure that after set-status + epoch tick we are guaranteed that a node leaves network map.
See #1755 for such situation.
Current workaround is to tick epoch twice or sleep for the block time.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the neofs-cli control set-status command and compare commands that already support the --await flag. Read issue #1755 and verify the behavior after set-status followed by one epoch tick. Done means the command can wait for completion so a node is guaranteed to leave the network map without requiring a second tick or a block-time sleep.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, distributed-systems
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.