-
Notifications
You must be signed in to change notification settings - Fork 108
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
Rosetta doesn't start during helm deployment #8259
Comments
I believe the mirrornode is not configured to ingest data from open access back in 09/2019 for mainnet, or from genesis in 02/2024 for the current testnet. This is expected behavior, not really a bug. |
@xin-hedera what is the right configuration for importer to ingest data? I didn't find proper values in the documentation. |
You need to set |
I thought rosetta was mandatory for production running. If rosetta is not mandatory, I keep it disabled. If I don't specify HEDERA_MIRROR_IMPORTER_STARTDATE date in the configuration, from which date it start to sync? If I want to sync from first available date, what date I should use? And how much postgres storage I should use to sync from first available date? Maybe you have some snapshots to restore from it? |
If I specify |
Got an error with
|
Description
I am using hedera-mirror-node chart to setup mirror node. When I enable rosetta, it doesn't start cause ReadinnesProbe failed. In the logs I see following message:
My values file is very simple:
Steps to reproduce
Additional context
No response
Hedera network
mainnet, testnet
Version
v0.103.0
Operating system
Linux
The text was updated successfully, but these errors were encountered: