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

Abierto
  • ¿Algo no está bien?
#147 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust
Área
backend, networking

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)"
Lenguaje dominante
Rust
Estrellas
104
Forks
40
Merge medio
18 min
PR fusionados (30 d)
2

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de txpipe/scrolls

Todos los issues de txpipe/scrolls

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.