We have finally put native History node to rest in peace as so many have done already, since it became unwieldy and unstable.
We have consolidated 3 API servers into Elasticsearch cluster to support our new History API:
So far our Elasticsearch cluster is synchronized up to 31.2M blocks and processing 7 blocks per second on average, which means it should catch up with Head block in a few days time.
We are using best compression mechanism available on Elasticsearch and only storing data actually used by History API. For example: storing accounts and transactions but not storing blocks since blocks are available via standard chain API.
And yet the whole cluster is currently taking about 3TB space and growing every day.
The new History api is available on our standard API server: api.eostribe.io
You can see more info on hardware specs and Data Center we use in our original post:
https://steemit.com/eos/@eostribe/eos-tribe-infrastructure-upgrade
Connect with us! We're building a better future on EOSIO.
I just resteemed your post!
Why? @eosbpnews aggregates updates of active EOS BPs and conveniently serves them in one place!
This service is provided by @eosoceania. If you think we are doing useful work, consider supporting us with a vote :)
For any inquiries/issues please reach out on Telegram or Discord.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Latest update: ES cluster on block 33099000 and just 1M+ blocks away from Head block.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Elasticsearch History API caught up to EOS head block on Jan 1, 2019.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit