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

unable to get goka running with the following error. #119

Closed
shubham7saxena opened this issue Mar 31, 2018 · 3 comments
Closed

unable to get goka running with the following error. #119

shubham7saxena opened this issue Mar 31, 2018 · 3 comments

Comments

@shubham7saxena
Copy link

Error creating processor: topic group-1-table has 50 partitions instead of 400 exit status 1

I see that this configuration comes from sarama. any particular reason I could be facing this.

@db7
Copy link
Collaborator

db7 commented Apr 1, 2018

The error is saying that your group-table has only 50 partitions (perhaps the default of your Kafka configuration if you have auto.create.topics.enable=true?) instead of the 400 partitions that your input streams have. Perhaps we should make the error message a bit more informative.

In goka, the input topics, joined tables and group tables have to have the same number of partitions (be copartitioned). You can output, of course, into topics with different number of partitions than the input.

Regarding your group table, you have two options: either you create the group table by hand with the same number of partitions as the input streams, or you let goka create for you by passing a zookeeper-based topic manager as option. Perhaps the wiki page can help you further.

@db7
Copy link
Collaborator

db7 commented Apr 4, 2018

@shubham7saxena any updates on this issue?

@db7
Copy link
Collaborator

db7 commented Aug 5, 2018

I'm assuming this problem is not relevant anymore. Please reopen if needed.

@db7 db7 closed this as completed Aug 5, 2018
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

2 participants