HeartSaVioR edited a comment on issue #19096: [SPARK-21869][SS] A cached Kafka 
producer should not be closed if any task is using it - adds inuse tracking.
URL: https://github.com/apache/spark/pull/19096#issuecomment-523236896
 
 
   > To say that we will never release a resource until a task says it's okay 
is inherently dangerous in a distributed system
   
   That's also the way how consumer instances are cached (that's why missing 
`close` brought file descriptor leak - #21997), though the logic is pretty much 
simpler since we don't allow co-use of instance (Kafka consumer is not 
thread-safe, whereas Kafka producer is thread-safe). Same behavior applies to 
Commons Pool as well, once you borrow the instance, pool never forces to 
destroy the instance until you return it.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to