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

Storm-Kafka-Client Trident Spout Seeks Incorrect Offset With UNCOMMITTED_LATEST Strategy

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.x
    • Fix Version/s: 2.0.0, 1.1.1, 1.2.0
    • Component/s: storm-kafka-client
    • Labels:
      None

      Description

      With UNCOMMITED_LATEST offset, Storm-Kafka-Client Trident Spout doesn't read all the data.
      See worker logs for of the same topology with UNCOMMITED_EARLIEST as well as UNCOMITTED_LATEST.
      The source topic has 3 partition and I publish data k000000-k000499(k000000, v000000 etc.)
      In particular for k000000 value the data is not picked by spout at all.

        Attachments

        1. worker_problem.log.zip
          447 kB
          Raghav Kumar Gautam
        2. worker_works.log.zip
          1.69 MB
          Raghav Kumar Gautam

          Issue Links

            Activity

              People

              • Assignee:
                hmclouro Hugo Louro
                Reporter:
                raghavgautam Raghav Kumar Gautam
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

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