Highly contested startup doesn't resolve itself properly

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Connectivity
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Not sure how to state this differently than the title. If we startup with 100 tasks (threads) on a non-discovered cluster, discovery takes longer to complete causing some (or all) of the requests to fail.

      There is something going on with a highly contested startup, likely as it relates to SDAM.

        1. Program.cs
          3 kB
          Robert Stam

              Assignee:
              Robert Stam
              Reporter:
              Craig Wilson
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: