Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RPC reconnection test #557

Closed
roman-khimov opened this issue May 3, 2023 · 2 comments
Closed

RPC reconnection test #557

roman-khimov opened this issue May 3, 2023 · 2 comments
Assignees
@vvarg229

Comments

@roman-khimov
Copy link
Member

See nspcc-dev/neofs-node#2325, we need to forcibly disconnect storage nodes from RPC nodes (10 times?) and check that they handle this fine.
@vvarg229 vvarg229 mentioned this issue Jul 6, 2023
Merged
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 6, 2023
@vvarg229
requirements: Add nsenter nspcc-dev#557
09e0a21 
Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 6, 2023
@vvarg229
failovers: Add test for RPC reconnection nspcc-dev#557
b32dbb0 
Added a new test in the failover network test suite to simulate and handle
RPC connection failures. It forcibly disconnects storage nodes from RPC nodes
repeatedly, and checks if the storage nodes are able to reconnect.

Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 11, 2023
@vvarg229
failovers: Add test for RPC reconnection nspcc-dev#557
c4ad171 
Added a new test in the failover network test suite to simulate and handle
RPC connection failures. It forcibly disconnects storage nodes from RPC nodes
repeatedly, and checks if the storage nodes are able to reconnect.

Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 19, 2023
@vvarg229
failovers: Add test for RPC reconnection nspcc-dev#557
5387c3f 
Added a new test in the failover network test suite to simulate and handle
RPC connection failures. It forcibly disconnects storage nodes from RPC nodes
repeatedly, and checks if the storage nodes are able to reconnect.

Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 19, 2023
@vvarg229
failovers: Add test for RPC reconnection nspcc-dev#557
e9d5bd5 
Added a new test in the failover network test suite to simulate and handle
RPC connection failures. It forcibly disconnects storage nodes from RPC nodes
repeatedly, and checks if the storage nodes are able to reconnect.

Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 24, 2023
@vvarg229
failovers: Add test for RPC reconnection nspcc-dev#557
6bcae10 
Added a new test in the failover network test suite to simulate and handle
RPC connection failures. It forcibly disconnects storage nodes from RPC nodes
repeatedly, and checks if the storage nodes are able to reconnect.

Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
@roman-khimov
Copy link
Member Author

Hmm, this seems to be fixed, but commit message had no "closes" or "fixes" notation.

@vvarg229
Copy link
Collaborator

Hmm, this seems to be fixed, but commit message had no "closes" or "fixes" notation.

Yes, this issue is really closed

vvarg229 added a commit to vvarg229/neofs-testcases that referenced this issue Jul 31, 2023
@vvarg229
failovers: Add test for RPC reconnection nspcc-dev#557
344141b 
Added a new test in the failover network test suite to simulate and handle
RPC connection failures. It forcibly disconnects storage nodes from RPC nodes
repeatedly, and checks if the storage nodes are able to reconnect.

Signed-off-by: Oleg Kulachenko <oleg@nspcc.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vvarg229 vvarg229

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roman-khimov @vvarg229