-
Notifications
You must be signed in to change notification settings - Fork 26
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
BCD indexer updates #537
BCD indexer updates #537
Conversation
Both indexers are able to index a private chain. BCD indexer needs private images with env variables to set the hostname for elastic/db/rabbitmq. Next release of BCD hub will have them, until then it is necessary to build your own containers: baking-bad/bcdhub#554 The indexer need to be activated in values.yaml and does not run by default. The default values.yaml has an explanation in comments.
My immediate need is to deploy an archive node; I need 300Gi of storage.
│ The files belonging to this database system will be owned by user "postgres". │ This user must also own the server process. │ The database cluster will be initialized with locale "en_US.utf8". │ The default database encoding has accordingly been set to "UTF8". │ The default text search configuration will be set to "english". │ Data page checksums are disabled. │ initdb: error: directory "/var/lib/postgresql/data" exists but is not empty │ It contains a lost+found directory, perhaps due to it being a mount point. │ Using a mount point directly as the data directory is not recommended. │ Create a subdirectory under the mount point. │ stream closed
There is no version 3.5.2 of containers.
There is currently no headless service for them.
Indexer + Baker/Node and Services updates
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.
As far as I can tell, this PR:
-
adds bcd pod to the tezos chart (optionally)
-
lints all python files it can find with black
-
re-adds a helm section that's gone from master (per_block_votes)
-
looks unvoluntary, should it be removed?
yes to everything except 3 and 4. I responded on the inline comment |
Working BCD indexer on their 4.3.0 release. They have a 4.4.0 release but I don't want to default to that version yet bec BCD right now is primarily for DMV. DMV is running older protocol right now that won't work with latest BCD release.