Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-9085

Log saver goes out of memory when many logs are out of order

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5.4
    • Fix Version/s: 3.5.5
    • Component/s: Log
    • Labels:
    • Release Notes:
      Fixed an out-of-memory issue for the log saver by adding a limit on the maximum number of events in-memory.
    • Rank:
      1|hzzy9z:

      Description

      Log saver keeps time based buckets of log events as the events are read from Kafka. There is a limit to the number of buckets kept in memory at any given time. However to maintain sorted order of log messages, any old messages fetched from Kafka are still added to in-memory buckets. We have seen cases where the time difference in adjacent log messages in Kafka is more than 10-20 seconds. This leads to more time based buckets than expected, and can lead to log saver going out of memory. To prevent this we can have a hard limit on the number of messages log saver will keep in memory.

        Attachments

          Activity

            People

            • Assignee:
              vinisha Vinisha Shah
              Reporter:
              vinisha Vinisha Shah
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: