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

SystemAdmin is not started properly in a few places

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 0.14.1
    • None
    • None

    Description

      https://github.com/apache/samza/pull/397 added a "start" and "stop" to the SystemAdmin interface. Most places got updated to manage the lifecycle. However, a few places were missed (or other changes were made more recently that did not correctly manage the lifecycle):

      1. CoordinatorStreamSystemConsumer starts a SystemAdmin in its "start" method. However, it uses SystemAdmin.getSystemStreamMetadata in "register", which is called before "start". This class properly stops SystemAdmin.
      2. SystemConsumerBench does not start/stop the SystemAdmin.
      3. TestRunner does not start/stop the SystemAdmin.

      Attachments

        Activity

          People

            Unassigned Unassigned
            cameronlee Cameron Lee
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m