[PHOENIX-3518] Memory Leak in RenewLeaseTask

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.7.0
• Fix Version/s: 4.9.1, 4.10.0

Environment

5.7.1-1.cdh5.7.1.p0.11 + jdk1.7.0_67
4.7.0-1.clabs_phoenix1.3.0.p0.000
CentOS Linux release 7.0.1406 (Core)
apache-tomcat-8.5.4 + jdk1.8.0_102

• Assignee: Unassigned
• Reporter: Jonathan Leech
• Created: 05/Dec/16 19:37
• Updated: 12/Dec/16 20:03
• Resolved: 12/Dec/16 20:03

Description

Looks like PHOENIX-2357 introduced a memory leak, at least for me... I end up with old gen filled up with objects - 100,000,000 instances each of WeakReference and LinkedBlockingQueue$Node, owned by ConnectionQueryServicesImpl.connectionsQueue. The PhoenixConnection referred to by the WeakReference is null for all but the few active connections. I don't see anything in the log - I can't confirm that it's logging properly though. Per the docs for ScheduledThreadPoolExecutor, if the run method throws an error, further executions are suppressed.