Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3518

Memory Leak in RenewLeaseTask

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.7.0
    • 4.9.1, 4.10.0
    • None
    • None
    • 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

    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.

      Attachments

        1. PHOENIX-3518_v2.patch
          4 kB
          Samarth Jain
        2. PHOENIX-3518.patch
          2 kB
          Samarth Jain

        Activity

          People

            Unassigned Unassigned
            jleech Jonathan Leech
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: