You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a service that automatically handles quickwit index existence. If quickwit index doesn't exist, it automatically creates index + kafka-source for it via REST API. The problem is that I decided to check kafka topic's consumers and it's empty.
Here is my kafka-source config:
I don't know where the problem is. If i'm right, quickwit has 1 consumer by default, and I don't want it to have more consumers to reduce hardware load.
Also, I pinged kafka in the quickwit docker-container and it worked, the domain name resolved successfully, so quickwit sees kafka.
Maybe I missed something?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a service that automatically handles quickwit index existence. If quickwit index doesn't exist, it automatically creates index + kafka-source for it via REST API. The problem is that I decided to check kafka topic's consumers and it's empty.
Here is my kafka-source config:
{ "version": "0.8", "source_id": "kafka-test", "source_type": "kafka", "params": { "topic": "test", "client_params": { "bootstrap.servers": "kafka:9092" } } }I don't know where the problem is. If i'm right, quickwit has 1 consumer by default, and I don't want it to have more consumers to reduce hardware load.
Also, I pinged kafka in the quickwit docker-container and it worked, the domain name resolved successfully, so quickwit sees kafka.
Maybe I missed something?
Beta Was this translation helpful? Give feedback.
All reactions