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.

Sign up for GitHub

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

Jump to bottom

Doesn't save until all the way synced (I think?) #11

Open
christianbundy opened this issue Sep 17, 2019 · 1 comment · May be fixed by #12
Open

Doesn't save until all the way synced (I think?) #11

christianbundy opened this issue Sep 17, 2019 · 1 comment · May be fixed by #12
Assignees
@christianbundy
Labels
bug

Comments

@christianbundy
Copy link
Member

I've seen this a bunch in Patchwork but never known why -- now I know!

During syncing most flumeviews will save their progress to disk, so if you restart the server while indexing it will start up where it left off. This doesn't seem to be the case with flumeview-reduce, which doesn't seem to save its progress until it's totally up-to-date.

Screenshot_2019-09-17 🏝️ Oasis
@christianbundy christianbundy self-assigned this Sep 17, 2019
This was referenced Sep 17, 2019
Closed
Open
@black-puppydog
Copy link
Contributor

black-puppydog commented Jan 25, 2021 •
edited
Loading

By now #16 is merged, allowing any flumeview-reduce index to make periodic writes. Now "all" that is left for patchwork is to find all the relevant views, and initialize them with periodic writes! Easy as pie! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@christianbundy christianbundy

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add write every 10K messages flumedb/flumeview-reduce
2 participants
@black-puppydog @christianbundy