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

fix: disable epoch info gc for now #2952

Merged
merged 5 commits into from
Jul 7, 2020
Merged

Conversation

bowenwang1996
Copy link
Collaborator

Currently we would garbage epoch information right after the epoch switch, which causes many problems including rpc not able to fetch chunks/blocks in the past epoch, not able to verify blocks in the past epoch, etc. I think it is safer to disable it for now and maybe consider implementing it properly when we redo the syncing code.

@gitpod-io
Copy link

gitpod-io bot commented Jul 7, 2020

@bowenwang1996 bowenwang1996 requested a review from Kouprin July 7, 2020 03:14
@bowenwang1996
Copy link
Collaborator Author

@Kouprin can you help fix the store validator code?

@Kouprin
Copy link
Member

Kouprin commented Jul 7, 2020

@bowenwang1996 please check if could we enable block_epoch_exists in Store Validator. The following steps may help:

  1. Uncomment block_epoch_exists check.
  2. Run custom Nightly.
  3. See all fails happened because of block_epoch_exists.
  4. Decide could we fix failures if any appear.
  5. Fix failures and enable block_epoch_exists OR describe why we cannot do that in comments for block_epoch_exists

@bowenwang1996
Copy link
Collaborator Author

@Kouprin I don't see why we cannot enable it. Do you want to do it in another PR or in this one?

@Kouprin
Copy link
Member

Kouprin commented Jul 7, 2020

@Kouprin I don't see why we cannot enable it. Do you want to do it in another PR or in this one?

I have no preferences. It might be better to have a separate PR as for another purpose but it's up to you.

Copy link
Collaborator

@SkidanovAlex SkidanovAlex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Undo the Cargo.lock change

@bowenwang1996
Copy link
Collaborator Author

@SkidanovAlex no Cargo.lock change after merging with master :)

@bowenwang1996 bowenwang1996 merged commit 25b517f into master Jul 7, 2020
@bowenwang1996 bowenwang1996 deleted the disable-epoch-info-gc branch July 7, 2020 20:29
bowenwang1996 added a commit that referenced this pull request Jul 7, 2020
Currently we would garbage epoch information right after the epoch switch, which causes many problems including rpc not able to fetch chunks/blocks in the past epoch, not able to verify blocks in the past epoch, etc. I think it is safer to disable it for now and maybe consider implementing it properly when we redo the syncing code.
chefsale pushed a commit that referenced this pull request Jul 8, 2020
Currently we would garbage epoch information right after the epoch switch, which causes many problems including rpc not able to fetch chunks/blocks in the past epoch, not able to verify blocks in the past epoch, etc. I think it is safer to disable it for now and maybe consider implementing it properly when we redo the syncing code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants