Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      we need a URL scheme for zookeeper. i think such a scheme could encode various forms of server lists as well as chroot.

        Issue Links

          Activity

          Alexander Shraer made changes -
          Link This issue is related to ZOOKEEPER-1355 [ ZOOKEEPER-1355 ]
          Benjamin Reed made changes -
          Link This issue is related to ZOOKEEPER-107 [ ZOOKEEPER-107 ]
          Benjamin Reed made changes -
          Link This issue relates to ZOOKEEPER-237 [ ZOOKEEPER-237 ]
          Benjamin Reed made changes -
          Field Original Value New Value
          Link This issue relates to ZOOKEEPER-146 [ ZOOKEEPER-146 ]
          Hide
          Benjamin Reed added a comment -

          I propose that the zookeeper URL has the following forms:

          zk://host:port,host:port,.../path
          and
          zk:URL!/path

          so if you construct a ZooKeeper object with zk://h1:2181,h2:2181,h3:2181/apps/myapp would create a ZooKeeper object pointed at the cluster made up of h1, h2, and h3 rooted at /apps/myapp. for backwards compatibility if we construct with h1:2181,h2:2181,h3:2181, it will be equivalent to zk://h1:2181,h2:2181,h3:2181/.

          if the list of hosts that make up the service are stored in the url http://abc.com/zkServers.txt, zk:http://abc.com/zkServers.txt!/ would be used to construct a ZooKeeper object.

          Show
          Benjamin Reed added a comment - I propose that the zookeeper URL has the following forms: zk://host:port,host:port,.../path and zk:URL!/path so if you construct a ZooKeeper object with zk://h1:2181,h2:2181,h3:2181/apps/myapp would create a ZooKeeper object pointed at the cluster made up of h1, h2, and h3 rooted at /apps/myapp. for backwards compatibility if we construct with h1:2181,h2:2181,h3:2181, it will be equivalent to zk://h1:2181,h2:2181,h3:2181/. if the list of hosts that make up the service are stored in the url http://abc.com/zkServers.txt , zk: http://abc.com/zkServers.txt!/ would be used to construct a ZooKeeper object.
          Benjamin Reed created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Benjamin Reed
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development