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

docs/node/sentry: Update config file for 23.0 #645

Merged
merged 2 commits into from
Feb 19, 2024

Conversation

amela
Copy link
Member

@amela amela commented Nov 28, 2023

Migrated with oasis-node config migrate and updated variables. Please review.

Copy link

netlify bot commented Nov 28, 2023

Deploy Preview for oasisprotocol-docs ready!

Name Link
🔨 Latest commit 6792806
🔍 Latest deploy log https://app.netlify.com/sites/oasisprotocol-docs/deploys/65d312f2325284000847f730
😎 Deploy Preview https://deploy-preview-645--oasisprotocol-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@amela amela requested a review from kostko November 28, 2023 08:24
- "{{ sentry_node_grpc_public_key }}@{{ sentry_node_private_ip }}:9009"

# Consensus backend.
mode: client
Copy link
Member

@ptrus ptrus Nov 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There were previously two configs, one for the sentry node, and one for the "normal" node, which is connecting to the sentry. Seems that one of the configs is missing now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, you are right. Added both configs and re-added comments.

@amela amela force-pushed the amela/update-config-sentry-23.0 branch from b5f4ceb to f3b4a30 Compare November 28, 2023 12:22
@amela amela requested a review from ptrus November 28, 2023 12:31
Copy link
Member

@ptrus ptrus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should work (didn't test it atm though)

disable_peer_exchange: true
persistent_peers:
- {{ sentry_node_tendermint_id }}@{{ sentry_node_private_ip }}:26656
prune:
Copy link
Member

@ptrus ptrus Nov 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does anyone know why did we have pruning configured here for the validator? e.g. for normal validator node we don't have pruning configured in the examples. I would just remove this "prune section" from this config (i think it's ok to keep in the other (sentry) config above, it makes more sense there).


edit actually idk. if it makes sense on the sentry to keep it this low. That means if validator is disconnected for ~1 hour it won't be able to sync from the sentry? Maybe remove prunning there as well, since it's not necessary.

consensus:
external_address: tcp://{{ external_address }}:26656
listen_address: tcp://0.0.0.0:26656
prune:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove pruning here as well since it's not really necessary and we usually don't have it configured in these example configs.

@amela amela force-pushed the amela/update-config-sentry-23.0 branch from ecdd90c to bbf0473 Compare February 19, 2024 08:33
@amela amela force-pushed the amela/update-config-sentry-23.0 branch from bbf0473 to 6792806 Compare February 19, 2024 08:36
@amela amela merged commit e0347b5 into main Feb 19, 2024
6 checks passed
@amela amela deleted the amela/update-config-sentry-23.0 branch February 19, 2024 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants