Minor: when cardano-node not available reconnection worker takes 100% CPU

Aperta
  • Qualcosa non va?
#147 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
rust
Ambito
backend, networking

Direzione di ricerca

Start by tracing the reconnection retry path indicated by the gasket::retries warnings and identify the worker that retries connections to cardano-node. The report shows repeated connection-refused errors and 100% CPU during an outage; determine what causes the excessive CPU and make retries avoid it. Done means reconnection continues while CPU use stays reasonable during an outage.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

So I noticed when there is an outage of cardano-node, scrolls tries to reconnect (this is great) but the small issue is that this reconnection watchdog/ daemon or worker in scrolls process is consuming way more CPU of the machine than it should.

image

mati@kajka:~$ sudo journalctl  -f -u scrolls
Jun 25 13:36:24 kajka scrolls[234390]: [2023-06-25T11:36:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:36:28 kajka scrolls[234390]: [2023-06-25T11:36:28Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:36:36 kajka scrolls[234390]: [2023-06-25T11:36:36Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:36:52 kajka scrolls[234390]: [2023-06-25T11:36:52Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:37:24 kajka scrolls[234390]: [2023-06-25T11:37:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:38:24 kajka scrolls[234390]: [2023-06-25T11:38:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:39:24 kajka scrolls[234390]: [2023-06-25T11:39:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:40:24 kajka scrolls[234390]: [2023-06-25T11:40:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:41:24 kajka scrolls[234390]: [2023-06-25T11:41:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Jun 25 13:42:24 kajka scrolls[234390]: [2023-06-25T11:42:24Z WARN  gasket::retries] retryable operation error: "network error: Connection refused (os error 111)"
Lingua principale
Rust
Stelle
104
Fork
40
Merge medio
18m
PR unite (30g)
2

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di txpipe/scrolls

Tutte le issue di txpipe/scrolls

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.