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

Workers are dropping messages during backfill #35

Open
gskril opened this issue May 12, 2024 · 0 comments
Open

Workers are dropping messages during backfill #35

gskril opened this issue May 12, 2024 · 0 comments

Comments

@gskril
Copy link
Owner

gskril commented May 12, 2024

Backfill with >1 concurrency will seemingly just miss all the links (or some other data type) for a fid(s) but get all casts, reactions, etc from that user.

The user(s) and data type(s) it skips are inconsistent and there are no errors in the logs. It's as if only part of the getFullProfileFromHub() function is running, or Postgres is somehow missing requests.

Verified by running a backfill with WORKER_CONCURRENCY=5, then running it again with WORKER_CONCURRENCY=1 and seeing that some tables had rows with newer updated_at values even though the message timestamp was old.

Thanks to @stephancill for finding the bug by comparing the number of rows in different tables after backfills with different concurrency values.

image

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