This issue is resolved in VMware NSX-T Data Center 2.4, available at
VMware Downloads.
Workaround:
The Edge VM can be rebooted to workaround the issue . As the issue can be hit again before upgarding to NSX-T 2.4, the recommendation is to add cron job on each LB edge node to periodically kill the lb-dispatcher process to avoid hitting memory leak in future. If the edge already hits the memory leak then killing just the lb-dispatcher will not help.
Steps:
1. check if "lb-dispatcher" process running
#pidof lb-dispatcher
2. collect edge log bundle (include core dump files) then clean up the core files (under /var/log/core)
3a: If "lb-dispatcher" is running , then kill the lb-dispatcher PID
#kill `pidof lb-dispatcher`
3b. If "lb-dispatcher" is NOT running , then reboot the Edge .
4. create a cron job of killing the lb-pid every night, till you upgrade to 2.4
On each Edge VM edit /etc/crontab
0 1 * * * /bin/sh kill `pidof lb-dispatcher` &> /dev/null
(This cron example will result in the LB service restarting every night at 1am resetting the memory usage and preventing the service crashing during business hours.)