Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-7919

Event stream on non-leader buffers event internally

    Details

      Description

      With Marathon 1.5.2, if a client attach to /v2/events of a non-leader server, it won't get event messages immediately.

      At the beginning, nothing received. After waiting for a relatively long time, a batch of events pop up. Then another long silent time window, and another batch of events.

      Acceptance

      For 1.5.3:

      Given we generate a events are published 100ms apart (when manually testing, potentially have a subscriber register and de-register every 100ms),
      And I query /v2/events from the non-leader
      Then I should receive events as they are emitted, 100ms apart, and not batched in to buffers

      For 1.6.0

      Given I query /v2/events from a non-leader
      then I receive a redirect to the leader

      Unit tests

      We can likely assert the buffering behavior fix via a unit test

        Attachments

          Activity

            People

            • Assignee:
              kjeschkies Karsten Jeschkies
              Reporter:
              fengyehong fengyehong
              Team:
              Orchestration Team
              Watchers:
              fengyehong, Karsten Jeschkies, Tim Harper
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: