Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-18712

Flink RocksDB statebackend memory leak issue

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Information Provided
    • 1.10.0
    • None
    • Runtime / State Backends

    Description

      When using RocksDB as our statebackend, we found it will lead to memory leak when restarting job (manually or in recovery case).

       

      How to reproduce:

      1. increase RocksDB blockcache size(e.g. 1G), it is easier to monitor and reproduce.
      2. start a job using RocksDB statebackend.
      3. when the RocksDB blockcache reachs maximum size, restart the job. and monitor the memory usage (k8s pod working set) of the TM.
      4. go through step 2-3 few more times. and memory will keep raising.

       

      Any solution or suggestion for this? Thanks!

      Attachments

        1. flink-demo-master.tgz
          3 kB
          Yun Tang

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. FLINK-19125 Avoid memory fragmentation when running flink docker image

          • Major - Major loss of function.
          • Closed

          Activity

            People

              yunta Yun Tang
              lio_sy Farnight
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: