Use different Sarama clients for admin API in topic and connection checker services
ppatierno opened this issue · 1 comments
ppatierno commented
Right now topic, connection checker and messages services uses the only one underlying Sarama client to create the corresponding admin API client and producer/consumer for doing their job.
Due to #94 we are going to close admin API client and recreate it when the problem occurs but in Sarama, when an admin API client is closed it automatically close the underlying client as well.
We have to different clients for the three main services in the canary: topic, connection checker and producer/consumer.