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

store: Setting default back to archive mode / no pruning #1590

Merged
merged 1 commit into from
Jul 9, 2018

Conversation

UnitylChaos
Copy link
Contributor

For testnets at least we should have the default be to keep all history so that bug hunting is easier.
Once other PRs (#1533 and #1580) come in we can have config / command line options to enable pruning manually for those that want to run lower disk usage nodes.

  • Updated all relevant documentation in docs
  • Updated all code comments where relevant
  • Wrote tests
  • Updated CHANGELOG.md
  • Updated Gaia/Examples
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)
  • Added appropriate labels to PR (ex. wip, ready-for-review, docs)

@cwgoes
Copy link
Contributor

cwgoes commented Jul 7, 2018

Can this be a configuration parameter instead of a constant that we have to change every time? Even for the testnets, I think we just need a few "full archive" nodes for debugging; most users can run with pruning enabled.

@UnitylChaos
Copy link
Contributor Author

Configuration parameter is definitely the plan, and what's being addressed in the other two PRs. I just thought we should have a quick change back so that we have the data, but I guess if everyone knows it's enabled, then we can just run some archive nodes for debugging purposes.

@ValarDragon
Copy link
Contributor

ValarDragon commented Jul 7, 2018

Looks like #1580 is almost done though, do you think it won't be done by next testnet?

@UnitylChaos
Copy link
Contributor Author

It could be merged now if approved. I would need to work on #1533 a bit to make use of it, but that could be done today if we aren't cutting the release till tonight or tomorrow.

@ValarDragon
Copy link
Contributor

ValarDragon commented Jul 7, 2018

internal testnet might be today or tomorrow, definitely not 7000. (Still need 1-2 days to build that genesis file, and a method to convert pubkeys)

@alexanderbez
Copy link
Contributor

Tbh, I think reverting this back makes sense for now until we find a reasonable approach on how to instantiate BaseApp in a clean and flexible manner (i.e. going with a context, using functional options, or some equivalent).

@alexanderbez
Copy link
Contributor

@jlandrews the build failed due to TestGaiaCLISend which is non-deterministic, so I reran the job. Will given an approval once passing.

@codecov
Copy link

codecov bot commented Jul 9, 2018

Codecov Report

Merging #1590 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1590   +/-   ##
========================================
  Coverage    64.18%   64.18%           
========================================
  Files          122      122           
  Lines         6674     6674           
========================================
  Hits          4284     4284           
  Misses        2145     2145           
  Partials       245      245

Copy link
Contributor

@alexanderbez alexanderbez left a comment

Choose a reason for hiding this comment

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

LGTM, but we certainly should come to a decision on how to make BaseApp construction more flexible.

Copy link
Contributor

@cwgoes cwgoes left a comment

Choose a reason for hiding this comment

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

Merging for now since the other two PRs look to still be in progress.

Once they're merged I think we should set pruning as the default and require a config change to run an archive node though.

@cwgoes cwgoes merged commit 0d6f99d into develop Jul 9, 2018
@cwgoes cwgoes deleted the jlandrews/defaultnoprune branch July 9, 2018 17:23
@alexanderbez
Copy link
Contributor

+1 @cwgoes

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