When configuring the kafka client disable the server #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #141
The overhead imposed by running the kafka server is unnecessary when only the kafka client is desired.
The best way to ensure resources used by the kafka server are cleaned up is to invoke the kafka servers
#unconfigure
method. Running the#unconfigure
method is only necessary if the kafka or zookeeper services are not running. It could be argued that the new method#configured?
only need check if the kafka service is running but to be safe I check if either kafka or zooker services are running.