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

Shutdown container on SIGTERM

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.8.0
    • 0.9.0
    • container
    • None

    Description

      Many runtime platforms (e.g. Mesos) will issue a SIGTERM to stop the Samza container process. In this case it would be good to try to cleanly shutdown the container, so that messages stop being processed, offsets and changelogs are committed, etc. This can be accomplished using TaskCoordinator.shutdown, but there currently is no glue between that and a SIGTERM or jvm shutdown hook.

      Here is the relevant mailing list thread: http://www.mail-archive.com/dev%40samza.incubator.apache.org/msg02246.html

      Attachments

        1. samza-506.patch
          0.9 kB
          Ewen Cheslack-Postava
        2. samza-506-3.patch
          3 kB
          Ewen Cheslack-Postava

        Issue Links

          depends upon

          Bug - A problem which impairs or prevents the functions of the product. SAMZA-513 BrokerProxy doesn't shut down

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              ewencp Ewen Cheslack-Postava
              zcox Zach Cox
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: