Add config instruction for archival node #742
Conversation
janewang
commented
Jun 8, 2021
janewang
commented
- Consolidating instructions to run an archival node under Run a Node doc
|
Your Render PR Server URL is https://docs-pr-742.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-c2vropia9d8gg9ed50q0. |
|
|
||
| ## Steps to Run an Archival Node | ||
|
|
||
| Make sure [`nearup`](https://github.com/near/nearup) is installed. You can install `nearup` by following the instructions at https://github.com/near/nearup. |
There was a problem hiding this comment.
We should add instructions on how to run an archival node without nearup as well.
There was a problem hiding this comment.
Should we also add the tracked shards in the documentation for the archival nodes? Here is seems we only mention the archive: true flag?
There was a problem hiding this comment.
@janewang feel free to ping me in chat or even schedule a meeting on running a neard standalone. I would really like to help on this, also provide maybe a guide on how to run it with systemd as well, as this is the best way to do it and that is how we manage all our current nodes on testnet and mainnet.
There was a problem hiding this comment.
Thanks @chefsale. Would love to connect on neard and systemd. Thanks in advance on this!
@bowenwang1996 Will merge this PR as it stands and add archival instructions with @chefsale's help. Would like to make announcements in validators channels today and link to the docs. Thanks!
* Increase storage cost for archival node * Clarify reason to run a node for development is to create apps with heavy reliance on RPC * Fix link to Foundation grant program
chefsale
left a comment
chefsale
left a comment
There was a problem hiding this comment.
LGTM, just please take a look at the comment here: https://github.com/near/docs/pull/742/files#r649917885, as I believe we should also mention the tracked_shards config alongside the archive flag,
* The rough cost estimate is calculated from the hourly cost posted on these websites for the instance type
Thanks, updated the config.json for archival. For server costs, I recalculated the estimated costs based on hourly for the instance type. AWS ended up the most expensive, which seems to be usually the case. Please take a look 3f9a963. Does this look alright to you @chefsale? |
@janewang Yes, this looks reasonable to me. I believe the SSDs are a bit more tricker, as there are two types of SSDs on GCP for example. But 300 dollars is a good rough estimate I believe, also the cost grows as we need to store more data from month to month and will need updating. Maybe we should mention that. 3 months from now it will be more archival data and more cost 😸 |
