-
Notifications
You must be signed in to change notification settings - Fork 1
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
Persist websocket cursor and resume upon restart #66
Labels
Comments
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 1, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 2, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 2, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 9, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 9, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 9, 2023
currently the cursor is saved every event to the database: i'm not sure how expensive this is, but we'll see :')
itstolf
added a commit
that referenced
this issue
Aug 10, 2023
strideynet
added a commit
that referenced
this issue
Aug 13, 2023
persist firehose cursor. closes #66
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we lose events during restarts or outages, let's persist the cursor and resume from last known position.
Potentially need to persist the cursor every X seconds (5 ?) to avoid hammering the database - the cursor can be a bit behind as long as we ensure we gracefully handle duplicate inserts.
The text was updated successfully, but these errors were encountered: