CLOSE_WAIT persists forever in kubernetes container [Linux] Even though my APP running in Java uses less heap space; My container memory is high always. On checking CLOSE_WAIT around 50 connections always persistent. Not sure if this is reason for high memory consumption in containers as per LENS metrics. If this CLOSE_WAIT is the possible suspect then is there any way to logoff these connections explicitly from linux or any utility can be developed to run as cron job [I know APP running in java is not closing ]
Tried setting up net.ipv4.tcp_keepalive_time but that doesn't solve CLOSE_WAIT