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.

Sign up for GitHub

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

Jump to bottom

Define separate config.json URLs for RPC, archival, and validator nodes #12070

Closed
6 tasks done
Tracked by #77
tayfunelmas opened this issue Sep 10, 2024 · 0 comments
Closed
6 tasks done
Tracked by #77

Define separate config.json URLs for RPC, archival, and validator nodes #12070

tayfunelmas opened this issue Sep 10, 2024 · 0 comments
Assignees
@tayfunelmas

Comments

@tayfunelmas
Copy link
Contributor

tayfunelmas commented Sep 10, 2024 •
edited
Loading

  • Create different config files from existing ones specific to RPC/archival/validator roles.
  • Define new URLs for each config file and upload new config files to the URLs
  • Modify neard init --download-config to specify the node type to download the right config.
  • Update validator documentation to refer to the new command arguments and reduce references to the explicit URLs.
  • Update indexer doc [link]
  • Update indexer doc [link].

For more context, see this Zulip thread
@tayfunelmas tayfunelmas self-assigned this Sep 10, 2024
@tayfunelmas tayfunelmas mentioned this issue Sep 10, 2024
Merged
@staffik staffik mentioned this issue Sep 10, 2024
Open
github-merge-queue bot pushed a commit that referenced this issue Sep 11, 2024
@tayfunelmas
feat: Update neard init to specify config file type to download (#12072)
a865808 
We change the `--download-config` parameter to take a string.
- `neard init --download-config validator` downloads the `config.json`
file for validators (tracking single shard, loading memtries).
- `neard init --download-config rpc` downloads the `config.json` file
for non-validator RPC nodes (tracking all shards, NOT loading memtries).
- `neard init --download-config archival` downloads the `config.json`
file for non-validator archival nodes (tracking all shards, NOT loading
memtries, archive field set to true).
- `neard init --download-config` (with no value) defaults to `validator`
config (for backwards compatibility).

We map the flag to a specific URL containing the config type. 
The new config files per config type can be found at
https://github.com/tayfunelmas/near-configs.
The new config files are already uploaded to AWS S3 with the new URLs.

NOTE: For indexer and chainsync-loadtest params, we use `rpc` config
type.

Next: We will update the Near validator documentation to use the new
flag value.

Tracking issue: #12070
This was referenced Sep 17, 2024
Merged
Closed
@github-actions github-actions bot mentioned this issue Oct 1, 2024
Open
@kobayurii kobayurii mentioned this issue Oct 3, 2024
Merged
tayfunelmas added a commit to near/docs that referenced this issue Nov 13, 2024
@tayfunelmas
Update run-near-lake.md to update confiig.json path for RPC config
786d26d 
With issue near/nearcore#12070, we separated the config.json files for different types of nodes (validator, RPC, archival).

Near-lake will use the RPC config, so updating the path to the config.json files.

Also removing a note because the issue referred to in the node is already closed (instead of updating the URLs in there as well).
@tayfunelmas tayfunelmas mentioned this issue Nov 13, 2024
Merged
bucanero pushed a commit to near/docs that referenced this issue Nov 13, 2024
@tayfunelmas
Update run-near-lake.md to update confiig.json path for RPC config (#…
a43d8e2 
…2303)

With issue near/nearcore#12070, we separated the config.json files for different types of nodes (validator, RPC, archival).

Near-lake will use the RPC config, so updating the path to the config.json files.

Also removing a note because the issue referred to in the node is already closed (instead of updating the URLs in there as well).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tayfunelmas tayfunelmas

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tayfunelmas