-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add Feeder logic #6
Labels
Comments
kostaskol
added a commit
that referenced
this issue
Sep 20, 2023
The relevant options have also been added to `config.tpl.yaml` Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 20, 2023
This struct contains methods for deserializing JSON strings into Events, as well as inserting/retrieving Events from the DB Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 20, 2023
The function Feeder.start_feeders spawns N threads, each of which immediately blocks on a Redis topic, waiting to pop the first available event. When an event is popped, it is deserialized into an Event object and written into a crossbeam channel, on the read-end of which exist processor threads. The number of feeder threads to be spawned is configurable through `workers:feeders` in `config.yaml` Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 20, 2023
It does not create a container for the processor itself, simply the required services (Postgres, Redis) Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 20, 2023
kostaskol
added a commit
that referenced
this issue
Sep 23, 2023
The relevant options have also been added to `config.tpl.yaml` Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 23, 2023
This struct contains methods for deserializing JSON strings into Events, as well as inserting/retrieving Events from the DB Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 23, 2023
The function Feeder.start_feeders spawns N threads, each of which immediately blocks on a Redis topic, waiting to pop the first available event. When an event is popped, it is deserialized into an Event object and written into a crossbeam channel, on the read-end of which exist processor threads. The number of feeder threads to be spawned is configurable through `workers:feeders` in `config.yaml` Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 23, 2023
It does not create a container for the processor itself, simply the required services (Postgres, Redis) Ref #6
kostaskol
added a commit
that referenced
this issue
Sep 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: