Uploaded image for project: 'Apache Storm'
  1. Apache Storm
  2. STORM-1950

Change response json of "Topology Lag" REST API to keyed by spoutId, topic, partition

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 2.0.0, 1.1.0
    • Component/s: storm-ui
    • Labels:
      None

      Description

      From code review for STORM-1945, there's an idea to change JSON response of "Topology Lag" API to keyed by topic, partition number.

      https://github.com/apache/storm/pull/1541#issuecomment-230983140

      I think also make result keyed by spout id would be good.
      Here's sample JSON of output after this issue is resolved.

      {
         "spout1":{
            "spoutId":"spout1",
            "spoutType":"KAFKA",
            "spoutLagResult":{
               "topic":{
                  "partition0":{
                     "consumerCommittedOffset":1175610,
                     "logHeadOffset":5634192,
                     "lag":4458582
                  },
                  "partition2":{
                     "consumerCommittedOffset":1175610,
                     "logHeadOffset":5634192,
                     "lag":4458582
                  }
               },
               "topic2":{
                  "partition0":{
                     "consumerCommittedOffset":1175610,
                     "logHeadOffset":5634192,
                     "lag":4458582
                  },
                  "partition2":{
                     "consumerCommittedOffset":1175610,
                     "logHeadOffset":5634192,
                     "lag":4458582
                  }
               }
            }
         }
      }
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kabhwan Jungtaek Lim
                Reporter:
                kabhwan Jungtaek Lim
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: