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

Existing container locality mapping is incorrect when building job model

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0, 1.1, 1.2
    • Fix Version/s: 1.3
    • Component/s: None
    • Labels:
      None

      Description

      When building the job model, the existing container locality is read, so that the task to container grouping can be calculated. However, the existing container locality mapping is incorrect, in that it always has one extra container than the job container count. If a grouper (e.g. GroupByContainerIds) uses the mapping to figure out the container models, then it might return the incorrect number of containers for the job model.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cameronlee Cameron Lee
                Reporter:
                cameronlee Cameron Lee
              • Votes:
                0 Vote for this issue
                Watchers:
                1 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 - 20m
                  20m