Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-12815

Change the default of topology.max.spout.pending from null to 1000 for Storm to prevent failures for Spout

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 2.0.0
    • 2.1.2
    • stacks
    • None

    Description

      PROBLEM: The deployed kafkaspout showed "failures" in the Storm UI, however there were no exceptions. The latency was high. Currently, topology.max.spout.pending is set to null via ambari and if the topology does not override it, it will not be set.
      At this point this can be set for kafkaspout configuration object in the topology code.

      Attachments

        1. AMBARI-12815.patch
          2 kB
          Dmytro Sen

        Issue Links

          Activity

            People

              dsen Dmytro Sen
              dsen Dmytro Sen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: