Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-2503

do a hard constraints on the number of myid which must between 0 and 255

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.4.9, 3.5.2, 3.4.11
    • None
    • server

    Description

      In ZK documentation, we have:

      "The myid file consists of a single line containing only the text of that machine's id. So myid of server 1 would contain the text "1" and nothing else. The id must be unique within the ensemble and should have a value between 1 and 255."

      This however is not enforced in code, which should be fixed either in documentation that we remove the restriction of the range 1-255 or in code we enforce such constraint.
      Discussion thread:
      http://zookeeper-user.578899.n2.nabble.com/Is-myid-actually-limited-to-1-255-td7581270.html

       

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. ZOOKEEPER-2901 Session ID that is negative causes mis-calculation of Ephemeral Type

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. ZOOKEEPER-260 document the recommended values for server id's

          • Major - Major loss of function.
          • Closed
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. ZOOKEEPER-2504 Enforce that server ids are unique in a cluster

          • Major - Major loss of function.
          • Patch Available
          links to

          Web Link GitHub Pull Request #832

          Activity

            People

              maoling Ling Mao
              hanm Michael Han
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2.5h
                  2.5h