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

Need ability to run RPC API when no 2/3 of nodes #1506

Closed
dimalit opened this issue Apr 28, 2023 · 3 comments · Fixed by #1540
Closed

Need ability to run RPC API when no 2/3 of nodes #1506

dimalit opened this issue Apr 28, 2023 · 3 comments · Fixed by #1540
Assignees
@olehnikolaiev
Labels
enhancement New feature or request epic:snapshots Snapshot functionality bugs and enhancements release:2.2

Comments

@dimalit
Copy link
Contributor

dimalit commented Apr 28, 2023 •
edited by DmytroNazarenko
Loading

When skaled starts when there are no 2/3 of nodes, it waits for them and doesn't allow others to send JSON RPC requests to it. In some situations this behavior can prevent chain from repairing. So, we need to start JSON-RPC before consensus
@dimalit dimalit self-assigned this Apr 28, 2023
@DmytroNazarenko DmytroNazarenko added enhancement New feature or request release:2.2 labels Apr 28, 2023
@DmytroNazarenko DmytroNazarenko assigned kladkogex and unassigned dimalit May 2, 2023
@DmytroNazarenko DmytroNazarenko moved this to Ready For Pickup in SKALE Engineering 🚀 May 2, 2023
@DmytroNazarenko DmytroNazarenko changed the title Need ability to provide snapshot when no 2/3 of nodes Need ability to provide RPC API when no 2/3 of nodes May 2, 2023
@DmytroNazarenko DmytroNazarenko changed the title Need ability to provide RPC API when no 2/3 of nodes Need ability to run RPC API when no 2/3 of nodes May 2, 2023
@DmytroNazarenko DmytroNazarenko added the epic:snapshots Snapshot functionality bugs and enhancements label May 4, 2023
@olehnikolaiev olehnikolaiev moved this from Ready For Pickup to In Progress in SKALE Engineering 🚀 Jun 6, 2023
@olehnikolaiev olehnikolaiev linked a pull request Jun 8, 2023 that will close this issue
Feature/1506 run rpc without 2/3 nodes #1540
Merged
@olehnikolaiev olehnikolaiev moved this from In Progress to Code Review in SKALE Engineering 🚀 Jun 8, 2023
@olehnikolaiev olehnikolaiev moved this from Code Review to In Progress in SKALE Engineering 🚀 Jun 19, 2023
@olehnikolaiev olehnikolaiev moved this from In Progress to Code Review in SKALE Engineering 🚀 Jun 19, 2023
@olehnikolaiev olehnikolaiev moved this from Code Review to Ready For Release Candidate in SKALE Engineering 🚀 Jun 20, 2023
@DmytroNazarenko DmytroNazarenko mentioned this issue Jun 20, 2023
Merged
@DmytroNazarenko
Copy link
Collaborator

3.17.0-beta.1

@DmytroNazarenko DmytroNazarenko moved this from Ready For Release Candidate to Merged To Release Candidate in SKALE Engineering 🚀 Jun 21, 2023
@EvgeniyZZ EvgeniyZZ moved this from Merged To Release Candidate to QA in SKALE Engineering 🚀 Jun 21, 2023
@oleksandrSydorenkoJ
Copy link

oleksandrSydorenkoJ commented Jul 11, 2023 •
edited
Loading

Verified on Regression network
Skale chain: wan-tasty-kitalpha
Version schain:3.17.0-beta.5

2023-07-11 15:00:44.298319   WARNING Error while trying to get snapshot signature from 1 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.298348   WARNING Error while trying to get snapshot signature from 2 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.298492   WARNING Error while trying to get snapshot signature from 3 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.298800   WARNING Error while trying to get snapshot signature from 4 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.298828   WARNING Error while trying to get snapshot signature from 5 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.298889   WARNING Error while trying to get snapshot signature from 6 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.299066   WARNING Error while trying to get snapshot signature from 7 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111
2023-07-11 15:00:44.299089   WARNING Error while trying to get snapshot signature from 8 : Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://111.111.11.1:1111


2023-07-11 15:00:45.026940   Got urls to download snapshot from 1 nodes 
2023-07-11 15:00:45.027039   Snapshot for block 1376107 is absent --- 
2023-07-11 15:00:45.027053   Will cleanup data dir and snapshots dir if needed
2023-07-11 15:00:45.052455   Will download snapshot from http://2.2.2.2:323

2023-07-11 15:04:34.700580   ... download progress ... 0 of 100

@EvgeniyZZ EvgeniyZZ moved this from QA to Done in SKALE Engineering 🚀 Aug 21, 2023
@PolinaKiporenko
Copy link
Contributor

https://github.com/skalenetwork/internal-support/blob/main/docs/specifications/skaled/v3.17.1/run-rpc-without-majority.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olehnikolaiev olehnikolaiev

Labels
enhancement New feature or request epic:snapshots Snapshot functionality bugs and enhancements release:2.2
Projects
SKALE Engineering 🚀
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/1506 run rpc without 2/3 nodes skalenetwork/skaled
6 participants
@dimalit @kladkogex @DmytroNazarenko @olehnikolaiev @oleksandrSydorenkoJ @PolinaKiporenko