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

Define getConfig Watcher behavior in chroot ZooKeeper

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • java client

    Description

      After ZOOKEEPER-4565, getConfig watcher will receive path for zookeeper config node "/zookeeper/config". But if the path getConfig watcher received is somewhat sensitive to chroot path.

      • With chroot path "/zookeeper", getConfig will receive path "/config".
      • With other chroot paths, getConfig will receive path "/zookeeper/config".

      I think we should define what path getConfig will get formally to avoid unnoticed behavior.

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue ZOOKEEPER-838 Chroot is an attribute of ClientCnxn

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. CURATOR-667 Background `getConfig` and `reconfig` could deliver abnormal path

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

          Bug - A problem which impairs or prevents the functions of the product. ZOOKEEPER-4565 Config watch path get truncated abnormally and fail chroot zookeeper client

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

          Web Link GitHub Pull Request #1996

          Activity

            People

              kezhuw Kezhu Wang
              kezhuw Kezhu Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

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