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.

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

Silent delay upon restart with prior db state of 24hours worth of pubnet #128

Closed
sreuland opened this issue Apr 9, 2024 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@sreuland
Copy link
Contributor

sreuland commented Apr 9, 2024

What version are you using?

20.3.5

What did you do?

Ran rpc for several days configured for pubnet, the on-disk db had maximum window of data allowed.
Stopped the rpc service.
Started the rpc service.

What did you expect to see?

new logs emitted and http service is listening right after the rpc service is started.

What did you see instead?

the rpc process is running on the o/s, but no logs emitted and no http service is bound/listening on tcp port, this state lasted for about 30minutes.

@sreuland sreuland added the bug Something isn't working label Apr 9, 2024
@sreuland sreuland moved this from Backlog to To Do in Platform Scrum Apr 9, 2024
@sreuland
Copy link
Contributor Author

I think this condition will be resolved/obsoleted by #115 which removes in-memory data storage in favor of all data on disk, @2opremio do you agree, since the delay observed here is caused by a blocking routine that copies db to memory first before it starts http service?

@2opremio
Copy link
Contributor

Yes, I agree!

@mollykarcher
Copy link
Contributor

Closing in lieu of #115

@github-project-automation github-project-automation bot moved this from To Do to Done in Platform Scrum May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

3 participants