when doing read retry upon exception, do not reuse same servers that gave errors

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Cluster Management
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      when doing retry there is no history of which servers were used, consequently the same bad server can be chosen 3 times and app gets exception.
      Solutions:

      • add "List<Server> triedServers" to call(), that defaults to null.
      • mark the server as not _ok right away, but that could lead to instability so dangerous.

            Assignee:
            Unassigned
            Reporter:
            Antoine Girbal (Inactive)
            None
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: