...
These write/read streams are from Vertx implementation, and are very coupled to Vertx KafkaProducer. Spring Kafka Template could not implement all contract methods of Write stream, so we will need to more deeply test this functionality.
Next steps
Currently some our modules close Kafka producers, some not, that can trigger different memory leaks.
Also regarding Vert Kafka documentation: When you are done with the producer, just close it, when all shared producers are closed, the resources will be released for you.
The new story has been created to address this:
, so based on these words, when there are active threads, Vertx keeps producer open and does not invoke physical close() method that is desired for us(some sort of connection pooling).Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-557
In some future we need conversation when to migrate our modules to Kafka streams or using Spring Kafka Template, that described in this spike