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

Update README.md #54

Merged
merged 1 commit into from
Nov 9, 2023
Merged

Update README.md #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,15 @@ Once the message is triggered a tombstone message (nil payload) will also be pro

For GO there is a clientlib for wrapping your kafka messages, check [clientlib](clientlib/) for more details.

ATTENTION !!

If you produce your messages using a Java or JavaScript library, you will need to pay attention to the partitioning of the producer for the scheduler. The scheduler is written in go and uses the official kafka library of confluent which is based on rdkafka, and the partitioning algorithm used by its producer is by default `consistent_random`. But most of java or javascript library is using `murmur2_random` algorithm. So configure the scheduler accordingly as follows to avoid issues:
```
export CONFIGURATION_FILE=config.yaml
cat config.yaml
kafka.producer.configuration:
partitioner: murmur2_random
```
# Architecture

The scheduler is basically a proxy consumer with its own topic.
Expand Down
Loading