Uploaded image for project: 'Ratis'
  1. Ratis
  2. RATIS-627

Rpc timeouts and leader election timeout configs are misleading

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 0.4.0
    • 0.4.0
    • server

    Description

      Currently, for a leader election to complete, timeouts are decided by min and max values given by rpc.timeout.min and rpc.timeout.max. But, there is a separate config for leader timeout given by "leader.election.timeout" after which the statemachine of the server is notified
      about leader election pending for a long time. The naming of the configs seem confusing at times.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            shashikant Shashikant Banerjee
            shashikant Shashikant Banerjee
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment