Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-3257

Tcp mem and socket domain socket leak in flume 1.7 and earlier versions.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.7.0
    • Fix Version/s: 1.8.0
    • Component/s: None
    • Labels:
      None
    • Release Note:
      The problem is already resolved in 1.8.0 as libthrift is upgraded to 0.9.3

      Description

      We'd like to report a resource(tcp mem, domain socket) leak caused by THRIFT-2402 . The problem is solved in 1.8.0 as it upgraded libthrift to 0.9.3, however we think it's still useful to share our experience with flume users. The sources which use libthrift server might encounter the resource leak problem, e.g. ScribeSource. The bug could be very serious (leading node unreachable in our case) while satisfying following conditions:

      1. Flume stop and start thrift server (e.g. scribe source) in the same process due to configuration reload and etc. Every stop and start action will cause resource leak.
      2. The server's traffic is very high. The leak might be quite big when the traffic is high.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              wzzdreamer zhenzhao wang
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: