Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-1112

BrokerProxy does not log fatal errors

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.12.0
    • Fix Version/s: 0.13.0
    • Component/s: None
    • Labels:
      None

      Description

      We hit an issue today where having a large backlog of messages to process caused an OutOfMemoryError in one our our jobs, presumably due to the BrokerProxy's default buffer size of 50k messages being too large. The issue though was that the error was not logged, and from the logs it appeared that the job just spontaneously exited.

      Looking at the BrokerProxy, there is no UncaughtExceptionHandler set for its thread, so any fatal errors only go to stderr.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                twbecker Tommy Becker
                Reporter:
                twbecker Tommy Becker
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: