Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-883

Group's handling of non-retryable errors and local timeout is incorrect

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.16.0
    • Component/s: None
    • Labels:
      None

      Description

      Currently both non-retryable errors and local timeout result in failed Futures and the client cannot differentiate the two.

      The clients of ZK master contender/detector need to terminate when facing non-retryable errors such as authenticate failures and retry when the ZK session times out locally (except for the leading master, who should terminate instead).

      The solution is to make Group's local session timeout behave exactly the same as sever-side session expiration which does not lead to failures. Therefore clients of the contender and detector should terminate when a failure is returned.

        Attachments

          Activity

            People

            • Assignee:
              xujyan Yan Xu
              Reporter:
              xujyan Yan Xu
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: