geo_borders.js fails in 2 shards sharded collections passthrough

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Query 2018-02-12, Query 2018-02-26
    • 16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The index build at geo_borders.js:24, which is expected to fail, may fail on only one of the shards. This can happen by chance if the out-of-bounds points that cause the failure all get assigned to the same shard, leaving one shard that has no illegal points.

              Assignee:
              David Storch
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: