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

load existing zulip data into RChain as a snapshot (incrementally?) #2

Open
dckc opened this issue Aug 3, 2020 · 1 comment
Open

Comments

@dckc
Copy link

dckc commented Aug 3, 2020

The design as of Jun 17 (36f3190) only works if you start the mirror when you initially boot zulip.

But suppose you have an existing zulip DB? How about a way to load it into RChain as a snapshot?

suggested by @steverosstalbot

@dckc
Copy link
Author

dckc commented Aug 3, 2020

Perhaps the snapshot tool could work incrementally; i.e.

  1. compare on-chain tables with off-chain tables; drop extras and create missing tables.
  2. For each table, compare on-chain keys with off-chain keys; drop extras and add missing records.
  3. For each record, compare on-chain data with off-chain data; replace any mismatched records.

Is there a way to avoid locking both sides for the duration? That could interfere with availability.

Perhaps timestamps could be used to optimize the record level data sync.

This could address the issue of mirror reliability (#49).

@dckc dckc changed the title load existing zulip data into RChain as a snapshot load existing zulip data into RChain as a snapshot (incrementally?) Aug 3, 2020
@jimscarver jimscarver transferred this issue from rchain-community/rvote Oct 3, 2020
jimscarver pushed a commit that referenced this issue Jul 30, 2021
…o/elliptic-6.5.3

build(deps): bump elliptic from 6.5.2 to 6.5.3 in /rchain-proto
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

No branches or pull requests

1 participant