Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

--initial-state improvements

See original GitHub issue

I used this amazing feature and it was simply magical to get a teku up to head in less than a minute. congrats.

there could be a couple of things that would make this even more magical

  • cache the state in the data dir, once it’s downloaded don’t download another state
  • if there is a an already synced chain, disregard the given intial state or something along those lines

it seems that if you give the state from an url, and the argument is still there after restarting the node, it sometimes (all the times?) crashes, probably because the initial state changes as it’s given like --initial-state=http://teku-beacon-archive:5051/teku/v1/beacon/states/finalized

the benefit of adding the initial state argument and leaving it is that you could have a statefulset of tekus that can scale up at a moment’s notice

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

ajsuttoncommented, Jan 26, 2021

Thanks for reporting this. Definitely worth looking into improving the usability here. There are some interactions with checking the weak subjectivity period which adds some security requirements around this (which is why Teku is currently always downloading the state again and exiting if it doesn’t match) but I suspect they can be handled in a better way without losing security. Will just require a bit of thought.

tzapucommented, Feb 2, 2021

the only thing i am worried about is that if the intial-state flag is set and the node restarts (usually after syncing completely) it fails to start. the rest of the potential issues seem like they would happen rarely and, in my head at least, sound like they should be handled manually. From that point of view “What if we only use --initial-state if the database doesn’t yet exist (ie first run) and ignore it afterwards.” sounds perfect to me

Read more comments on GitHub >

github_iconTop Results From Across the Web

New Feature Releases - Initial State
Mouse Wheel Zoom Enhancements in Waves/Lines. Your mouse wheel will now zoom in and out of your data by default in Waves and...
Read more >
Initial State | Software Reviews & Alternatives - Crozdesk
Initial State Review: 'Data Analytics for the Internet of Things: Stream data from your ... The score for this software has improved over...
Read more >
React: Get initialstate after state has changed - Stack Overflow
No, the initial state isn't stored -- but you can call this.getInitialState() if you want to reexecute the function.
Read more >
[APM] Improvements in useFetcher and how we pass fetching ...
Problem We break up the return value from useFetcher (data and status) and then pass them down separately. We then come up with...
Read more >
configureStore - Redux Toolkit
An optional initial state value to be passed to the Redux createStore function. enhancers ​. An optional array of Redux store enhancers, or...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found