Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Log what's going on at ct-server startup #1351

Open
robstradling opened this issue Dec 2, 2016 · 0 comments
Open

Log what's going on at ct-server startup #1351

robstradling opened this issue Dec 2, 2016 · 0 comments
Assignees

Comments

@robstradling
Copy link
Contributor

Al wrote in an email to me:
"Note that depending on how many entries are in the tree it can take a long time for nodes to restart as they scan the entire local db to verify it and rebuild the node's merkletree and indices. Sadly there's no logged message to indicate it's doing this, someone should change that, but you'll see the CPU usage pegged high while this is happening."

@pphaneuf pphaneuf self-assigned this Dec 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants