-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat: ✨ add maintenance mode to node #389
base: main
Are you sure you want to change the base?
Conversation
Maintenance mode allows node operators to run their nodes without them interacting with the rest of the network. This allows them to do manual changes to the file or forest storage in case of inconsistencies between what's on-chain vs the local state.
if self.maintenance_mode { | ||
info!(target: LOG_TARGET, "🔒 Maintenance mode is enabled. Skipping message processing."); | ||
return; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could allow commands being sent to the BlockchainService. Just in case we need that functionality while in maintenance.
if self.maintenance_mode { | ||
info!(target: LOG_TARGET, "🔒 Maintenance mode is enabled. Skipping processing ofblock import #{}: {}", block_number, block_hash); | ||
return; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would apply this boolean further up, to basically not include the block import and finality events in the queue. Cause this way it is still possible that the node will attempt some action in the initial sync.
Maintenance mode allows node operators to run their nodes without them interacting with the rest of the network. This allows them to do manual changes to the file or forest storage in case of inconsistencies between what's on-chain vs the local state.
TODO: