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.

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

Fast sync does not import logs #3500

Closed
ethernomad opened this issue Dec 30, 2016 · 4 comments
Closed

Fast sync does not import logs #3500

ethernomad opened this issue Dec 30, 2016 · 4 comments

Comments

@ethernomad
Copy link
Contributor

System information

Geth
Version: 1.5.5-stable
Git Commit: ff07d54
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.7.3
OS: linux
GOPATH=
GOROOT=/usr/lib/go-1.7

Expected behaviour

After performing a fast sync old logs should be available.

In the original pull request #1889 says:

The resulting databases contain the entire blockchain (all blocks, all uncles, all transactions), every transaction receipt and generated logs, and the entire state trie of the head 1024 blocks. This allows a fast synced node to act as a full archive node from all intents and purposes.

Actual behaviour

Logs from blocks that were imported via the "fast" method are not available.

This is a major disadvantage to fast sync. Can it be made an option?

Thanks

@karalabe
Copy link
Member

karalabe commented Jan 3, 2017

They should definitely be available. If not, something's broken. I'll look into it.

@bas-vk
Copy link
Member

bas-vk commented Jan 3, 2017

Maybe there is some kind of relation with #3502. On my local machine I get all logs independent if the node was synced with fast sync or not.

@fjl
Copy link
Contributor

fjl commented Jan 17, 2017

@ethernomad in #3563 (comment), you linked to a reddit post claiming that logs are missing after fast sync. Did you open this issue speculatively? Can you verify that running geth --fast imports logs correctly on your machine?

@stale
Copy link

stale bot commented Mar 5, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status:inactive label Mar 5, 2018
@stale stale bot closed this as completed Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants