Skip to content
This repository has been archived by the owner on Oct 4, 2019. It is now read-only.

Store only consensus data while serialize state #1172

Closed
zxcat opened this issue Mar 11, 2019 · 2 comments
Closed

Store only consensus data while serialize state #1172

zxcat opened this issue Mar 11, 2019 · 2 comments
Assignees

Comments

@zxcat
Copy link

zxcat commented Mar 11, 2019

Code implemented in #1133 serializes almost all data stored in state. But node can be configured to clear votes and other data, which is no more needed for consensus. This makes produced serialized state file dependent on config settings.
Update state serialization to produce file, which doesn't depend on config settings.

@zxcat zxcat self-assigned this Mar 11, 2019
@zxcat
Copy link
Author

zxcat commented Jun 3, 2019

  1. remove non-consensus votes
  2. remove memo from savings_withdraw_object:
    if (_db.store_memo_in_savings_withdraws()) {

zxcat added a commit that referenced this issue Jun 3, 2019
+ store `depth` and `children` fields for closed posts #1302
+ don't store non-consensus votes #1172
+ don't store savings withdraw memo #1172
+ better custom packer for comment object (compact storage)
+ removed indexes which are not needed
@zxcat
Copy link
Author

zxcat commented Jun 3, 2019

PR #1325

afalaleev added a commit that referenced this issue Jun 4, 2019
Serialized state: add comment data & remove non-consensus #1302 #1172
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants