Investigate slow start up of the GraphQL server in beta 3 #1428
Assignees
Comments
xgreenx
added a commit
that referenced
this issue
Oct 27, 2023
Closes #1428 Call the `flush` function during the end of the `FuelService` to move the processing of WAL and SST fiels from the node's launching to the node's shutdown. Added additional logs to track the performance of the starting/shutdown process.
crypto523
pushed a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
Closes FuelLabs/fuel-core#1428 Call the `flush` function during the end of the `FuelService` to move the processing of WAL and SST fiels from the node's launching to the node's shutdown. Added additional logs to track the performance of the starting/shutdown process.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The authority node in beta 3 experienced a long launch after the restart. Because the launch was longer than 30 seconds, the GraphQL server, required for liveness check, was unavailable. After 30 seconds the liveness check failed and restarted the node again. It had been happening until we removed the liveness check.
There was only one log - the version of the image:
It seems something before starting the services or one of the services took a lot of time to start. Maybe opening the rocksdb after the invalid closing of it takes a lot of time.
The text was updated successfully, but these errors were encountered: