-
Notifications
You must be signed in to change notification settings - Fork 443
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
"cluster-topic-manipulation-service" issue #348
Comments
This is your first issue in the repository. Thank you for raising this issue.' first issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello team, I faced the issue with cluster-topic-manipulation-service it doesn't work for me at all.
So when I'm configuring this it doesn't create a topic for iterations and didn't send any info into "reporter-service" and to "statsd-service" metrics accordingly. However, the other configuration works as it should. Could you please check my config file, maybe I made some mistakes:
In addition, I have a question, is it possible that the "cluster-topic-manipulation-service" would work with Kafka brokers only, without zookeepers? This is very important for our infrastructure.
Also, I noticed that there is no possibility to reload service configuration without application restart. Our case is necessary for pkcs12 Keystore reloading every 24 hours. Could you please add this possibility in future releases?
The text was updated successfully, but these errors were encountered: