You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@zookeeper.apache.org by an...@apache.org on 2018/11/06 17:50:33 UTC
[14/16] zookeeper git commit: ZOOKEEPER-3155: Remove Forrest XMLs and their build process from the …
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/recipes.html
----------------------------------------------------------------------
diff --git a/docs/recipes.html b/docs/recipes.html
deleted file mode 100644
index df494e7..0000000
--- a/docs/recipes.html
+++ /dev/null
@@ -1,1024 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.9">
-<meta name="Forrest-skin-name" content="pelt">
-<title>ZooKeeper Recipes and Solutions</title>
-<link type="text/css" href="skin/basic.css" rel="stylesheet">
-<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
-<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
-<link type="text/css" href="skin/profile.css" rel="stylesheet">
-<script src="skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="skin/fontsize.js" language="javascript" type="text/javascript"></script>
-<link rel="shortcut icon" href="images/favicon.ico">
-</head>
-<body onload="init()">
-<script type="text/javascript">ndeSetTextSize();</script>
-<div id="top">
-<!--+
- |breadtrail
- +-->
-<div class="breadtrail">
-<a href="http://www.apache.org/">Apache</a> > <a href="http://zookeeper.apache.org/">ZooKeeper</a> > <a href="http://zookeeper.apache.org/">ZooKeeper</a><script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
-</div>
-<!--+
- |header
- +-->
-<div class="header">
-<!--+
- |start group logo
- +-->
-<div class="grouplogo">
-<a href="http://hadoop.apache.org/"><img class="logoImage" alt="Hadoop" src="images/hadoop-logo.jpg" title="Apache Hadoop"></a>
-</div>
-<!--+
- |end group logo
- +-->
-<!--+
- |start Project Logo
- +-->
-<div class="projectlogo">
-<a href="http://zookeeper.apache.org/"><img class="logoImage" alt="ZooKeeper" src="images/zookeeper_small.gif" title="ZooKeeper: distributed coordination"></a>
-</div>
-<!--+
- |end Project Logo
- +-->
-<!--+
- |start Search
- +-->
-<div class="searchbox">
-<form action="http://www.google.com/search" method="get" class="roundtopsmall">
-<input value="zookeeper.apache.org" name="sitesearch" type="hidden"><input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google">
- <input name="Search" value="Search" type="submit">
-</form>
-</div>
-<!--+
- |end search
- +-->
-<!--+
- |start Tabs
- +-->
-<ul id="tabs">
-<li>
-<a class="unselected" href="http://zookeeper.apache.org/">Project</a>
-</li>
-<li>
-<a class="unselected" href="https://cwiki.apache.org/confluence/display/ZOOKEEPER/">Wiki</a>
-</li>
-<li class="current">
-<a class="selected" href="index.html">ZooKeeper 3.6 Documentation</a>
-</li>
-</ul>
-<!--+
- |end Tabs
- +-->
-</div>
-</div>
-<div id="main">
-<div id="publishedStrip">
-<!--+
- |start Subtabs
- +-->
-<div id="level2tabs"></div>
-<!--+
- |end Endtabs
- +-->
-<script type="text/javascript"><!--
-document.write("Last Published: " + document.lastModified);
-// --></script>
-</div>
-<!--+
- |breadtrail
- +-->
-<div class="breadtrail">
-
-
- </div>
-<!--+
- |start Menu, mainarea
- +-->
-<!--+
- |start Menu
- +-->
-<div id="menu">
-<div onclick="SwitchMenu('menu_1.1', 'skin/')" id="menu_1.1Title" class="menutitle">Overview</div>
-<div id="menu_1.1" class="menuitemgroup">
-<div class="menuitem">
-<a href="index.html">Welcome</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperOver.html">Overview</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperStarted.html">Getting Started</a>
-</div>
-<div class="menuitem">
-<a href="releasenotes.html">Release Notes</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_selected_1.2', 'skin/')" id="menu_selected_1.2Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">Developer</div>
-<div id="menu_selected_1.2" class="selectedmenuitemgroup" style="display: block;">
-<div class="menuitem">
-<a href="api/index.html">API Docs</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperProgrammers.html">Programmer's Guide</a>
-</div>
-<div class="menuitem">
-<a href="javaExample.html">Java Example</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperTutorial.html">Barrier and Queue Tutorial</a>
-</div>
-<div class="menupage">
-<div class="menupagetitle">Recipes</div>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.3', 'skin/')" id="menu_1.3Title" class="menutitle">Admin & Ops</div>
-<div id="menu_1.3" class="menuitemgroup">
-<div class="menuitem">
-<a href="zookeeperAdmin.html">Administrator's Guide</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperQuotas.html">Quota Guide</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperJMX.html">JMX</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperObservers.html">Observers Guide</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperReconfig.html">Dynamic Reconfiguration</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.4', 'skin/')" id="menu_1.4Title" class="menutitle">Contributor</div>
-<div id="menu_1.4" class="menuitemgroup">
-<div class="menuitem">
-<a href="zookeeperInternals.html">ZooKeeper Internals</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.5', 'skin/')" id="menu_1.5Title" class="menutitle">Miscellaneous</div>
-<div id="menu_1.5" class="menuitemgroup">
-<div class="menuitem">
-<a href="https://cwiki.apache.org/confluence/display/ZOOKEEPER">Wiki</a>
-</div>
-<div class="menuitem">
-<a href="https://cwiki.apache.org/confluence/display/ZOOKEEPER/FAQ">FAQ</a>
-</div>
-<div class="menuitem">
-<a href="http://zookeeper.apache.org/mailing_lists.html">Mailing Lists</a>
-</div>
-</div>
-<div id="credit"></div>
-<div id="roundbottom">
-<img style="display: none" class="corner" height="15" width="15" alt="" src="skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
-<!--+
- |alternative credits
- +-->
-<div id="credit2"></div>
-</div>
-<!--+
- |end Menu
- +-->
-<!--+
- |start content
- +-->
-<div id="content">
-<div title="Portable Document Format" class="pdflink">
-<a class="dida" href="recipes.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
- PDF</a>
-</div>
-<h1>ZooKeeper Recipes and Solutions</h1>
-<div id="front-matter">
-<div id="minitoc-area">
-<ul class="minitoc">
-<li>
-<a href="#ch_recipes">A Guide to Creating Higher-level Constructs with ZooKeeper</a>
-<ul class="minitoc">
-<li>
-<a href="#sc_recipes_errorHandlingNote">Important Note About Error Handling</a>
-</li>
-<li>
-<a href="#sc_outOfTheBox">Out of the Box Applications: Name Service, Configuration, Group
- Membership</a>
-</li>
-<li>
-<a href="#sc_recipes_eventHandles">Barriers</a>
-<ul class="minitoc">
-<li>
-<a href="#sc_doubleBarriers">Double Barriers</a>
-</li>
-</ul>
-</li>
-<li>
-<a href="#sc_recipes_Queues">Queues</a>
-<ul class="minitoc">
-<li>
-<a href="#sc_recipes_priorityQueues">Priority Queues</a>
-</li>
-</ul>
-</li>
-<li>
-<a href="#sc_recipes_Locks">Locks</a>
-<ul class="minitoc">
-<li>
-<a href="#sc_recipes_GuidNote">Recoverable Errors and the GUID</a>
-</li>
-<li>
-<a href="#Shared+Locks">Shared Locks</a>
-</li>
-<li>
-<a href="#sc_revocableSharedLocks">Revocable Shared Locks</a>
-</li>
-</ul>
-</li>
-<li>
-<a href="#sc_recipes_twoPhasedCommit">Two-phased Commit</a>
-</li>
-<li>
-<a href="#sc_leaderElection">Leader Election</a>
-</li>
-</ul>
-</li>
-</ul>
-</div>
-</div>
-
-
-
-
-
-<a name="ch_recipes"></a>
-<h2 class="h3">A Guide to Creating Higher-level Constructs with ZooKeeper</h2>
-<div class="section">
-<p>In this article, you'll find guidelines for using
- ZooKeeper to implement higher order functions. All of them are conventions
- implemented at the client and do not require special support from
- ZooKeeper. Hopfully the community will capture these conventions in client-side libraries
- to ease their use and to encourage standardization.</p>
-<p>One of the most interesting things about ZooKeeper is that even
- though ZooKeeper uses <em>asynchronous</em> notifications, you
- can use it to build <em>synchronous</em> consistency
- primitives, such as queues and locks. As you will see, this is possible
- because ZooKeeper imposes an overall order on updates, and has mechanisms
- to expose this ordering.</p>
-<p>Note that the recipes below attempt to employ best practices. In
- particular, they avoid polling, timers or anything else that would result
- in a "herd effect", causing bursts of traffic and limiting
- scalability.</p>
-<p>There are many useful functions that can be imagined that aren't
- included here - revocable read-write priority locks, as just one example.
- And some of the constructs mentioned here - locks, in particular -
- illustrate certain points, even though you may find other constructs, such
- as event handles or queues, a more practical means of performing the same
- function. In general, the examples in this section are designed to
- stimulate thought.</p>
-<a name="sc_recipes_errorHandlingNote"></a>
-<h3 class="h4">Important Note About Error Handling</h3>
-<p>When implementing the recipes you must handle recoverable exceptions
- (see the <a href="https://cwiki.apache.org/confluence/display/ZOOKEEPER/FAQ">FAQ</a>). In
- particular, several of the recipes employ sequential ephemeral
- nodes. When creating a sequential ephemeral node there is an error case in
- which the create() succeeds on the server but the server crashes before
- returning the name of the node to the client. When the client reconnects its
- session is still valid and, thus, the node is not removed. The implication is
- that it is difficult for the client to know if its node was created or not. The
- recipes below include measures to handle this.</p>
-<a name="sc_outOfTheBox"></a>
-<h3 class="h4">Out of the Box Applications: Name Service, Configuration, Group
- Membership</h3>
-<p>Name service and configuration are two of the primary applications
- of ZooKeeper. These two functions are provided directly by the ZooKeeper
- API.</p>
-<p>Another function directly provided by ZooKeeper is <em>group
- membership</em>. The group is represented by a node. Members of the
- group create ephemeral nodes under the group node. Nodes of the members
- that fail abnormally will be removed automatically when ZooKeeper detects
- the failure.</p>
-<a name="sc_recipes_eventHandles"></a>
-<h3 class="h4">Barriers</h3>
-<p>Distributed systems use <em>barriers</em>
- to block processing of a set of nodes until a condition is met
- at which time all the nodes are allowed to proceed. Barriers are
- implemented in ZooKeeper by designating a barrier node. The
- barrier is in place if the barrier node exists. Here's the
- pseudo code:</p>
-<ol>
-
-<li>
-
-<p>Client calls the ZooKeeper API's <strong>exists()</strong> function on the barrier node, with
- <em>watch</em> set to true.</p>
-
-</li>
-
-
-<li>
-
-<p>If <strong>exists()</strong> returns false, the
- barrier is gone and the client proceeds</p>
-
-</li>
-
-
-<li>
-
-<p>Else, if <strong>exists()</strong> returns true,
- the clients wait for a watch event from ZooKeeper for the barrier
- node.</p>
-
-</li>
-
-
-<li>
-
-<p>When the watch event is triggered, the client reissues the
- <strong>exists( )</strong> call, again waiting until
- the barrier node is removed.</p>
-
-</li>
-
-</ol>
-<a name="sc_doubleBarriers"></a>
-<h4>Double Barriers</h4>
-<p>Double barriers enable clients to synchronize the beginning and
- the end of a computation. When enough processes have joined the barrier,
- processes start their computation and leave the barrier once they have
- finished. This recipe shows how to use a ZooKeeper node as a
- barrier.</p>
-<p>The pseudo code in this recipe represents the barrier node as
- <em>b</em>. Every client process <em>p</em>
- registers with the barrier node on entry and unregisters when it is
- ready to leave. A node registers with the barrier node via the <strong>Enter</strong> procedure below, it waits until
- <em>x</em> client process register before proceeding with
- the computation. (The <em>x</em> here is up to you to
- determine for your system.)</p>
-<table class="ForrestTable" cellspacing="1" cellpadding="4">
-
-
-<tr>
-
-<td><strong>Enter</strong></td>
-
- <td><strong>Leave</strong></td>
-
-</tr>
-
-
-<tr>
-
-<td>
-<ol>
-
-<li>
-
-<p>Create a name <em><em>n</em> =
- <em>b</em>+“/”+<em>p</em></em>
-</p>
-
-</li>
-
-
-<li>
-
-<p>Set watch: <strong>exists(<em>b</em> + ‘‘/ready’’,
- true)</strong>
-</p>
-
-</li>
-
-
-<li>
-
-<p>Create child: <strong>create(
- <em>n</em>, EPHEMERAL)</strong>
-</p>
-
-</li>
-
-
-<li>
-
-<p>
-<strong>L = getChildren(b,
- false)</strong>
-</p>
-
-</li>
-
-
-<li>
-
-<p>if fewer children in L than<em>
- x</em>, wait for watch event</p>
-
-</li>
-
-
-<li>
-
-<p>else <strong>create(b + ‘‘/ready’’,
- REGULAR)</strong>
-</p>
-
-</li>
-
-</ol>
-</td>
-
- <td>
-<ol>
-
-<li>
-
-<p>
-<strong>L = getChildren(b,
- false)</strong>
-</p>
-
-</li>
-
-
-<li>
-
-<p>if no children, exit</p>
-
-</li>
-
-
-<li>
-
-<p>if <em>p</em> is only process node in
- L, delete(n) and exit</p>
-
-</li>
-
-
-<li>
-
-<p>if <em>p</em> is the lowest process
- node in L, wait on highest process node in L</p>
-
-</li>
-
-
-<li>
-
-<p>else <strong>delete(<em>n</em>) </strong>if
- still exists and wait on lowest process node in L</p>
-
-</li>
-
-
-<li>
-
-<p>goto 1</p>
-
-</li>
-
-</ol>
-</td>
-
-</tr>
-
-
-</table>
-<p>On entering, all processes watch on a ready node and
- create an ephemeral node as a child of the barrier node. Each process
- but the last enters the barrier and waits for the ready node to appear
- at line 5. The process that creates the xth node, the last process, will
- see x nodes in the list of children and create the ready node, waking up
- the other processes. Note that waiting processes wake up only when it is
- time to exit, so waiting is efficient.
- </p>
-<p>On exit, you can't use a flag such as <em>ready</em>
- because you are watching for process nodes to go away. By using
- ephemeral nodes, processes that fail after the barrier has been entered
- do not prevent correct processes from finishing. When processes are
- ready to leave, they need to delete their process nodes and wait for all
- other processes to do the same.</p>
-<p>Processes exit when there are no process nodes left as children of
- <em>b</em>. However, as an efficiency, you can use the
- lowest process node as the ready flag. All other processes that are
- ready to exit watch for the lowest existing process node to go away, and
- the owner of the lowest process watches for any other process node
- (picking the highest for simplicity) to go away. This means that only a
- single process wakes up on each node deletion except for the last node,
- which wakes up everyone when it is removed.</p>
-<a name="sc_recipes_Queues"></a>
-<h3 class="h4">Queues</h3>
-<p>Distributed queues are a common data structure. To implement a
- distributed queue in ZooKeeper, first designate a znode to hold the queue,
- the queue node. The distributed clients put something into the queue by
- calling create() with a pathname ending in "queue-", with the
- <em>sequence</em> and <em>ephemeral</em> flags in
- the create() call set to true. Because the <em>sequence</em>
- flag is set, the new pathnames will have the form
- _path-to-queue-node_/queue-X, where X is a monotonic increasing number. A
- client that wants to be removed from the queue calls ZooKeeper's <strong>getChildren( )</strong> function, with
- <em>watch</em> set to true on the queue node, and begins
- processing nodes with the lowest number. The client does not need to issue
- another <strong>getChildren( )</strong> until it exhausts
- the list obtained from the first <strong>getChildren(
- )</strong> call. If there are are no children in the queue node, the
- reader waits for a watch notification to check the queue again.</p>
-<div class="note">
-<div class="label">Note</div>
-<div class="content">
-
-<p>There now exists a Queue implementation in ZooKeeper
- recipes directory. This is distributed with the release --
- src/recipes/queue directory of the release artifact.
- </p>
-
-</div>
-</div>
-<a name="sc_recipes_priorityQueues"></a>
-<h4>Priority Queues</h4>
-<p>To implement a priority queue, you need only make two simple
- changes to the generic <a href="#sc_recipes_Queues">queue
- recipe</a> . First, to add to a queue, the pathname ends with
- "queue-YY" where YY is the priority of the element with lower numbers
- representing higher priority (just like UNIX). Second, when removing
- from the queue, a client uses an up-to-date children list meaning that
- the client will invalidate previously obtained children lists if a watch
- notification triggers for the queue node.</p>
-<a name="sc_recipes_Locks"></a>
-<h3 class="h4">Locks</h3>
-<p>Fully distributed locks that are globally synchronous, meaning at
- any snapshot in time no two clients think they hold the same lock. These
- can be implemented using ZooKeeeper. As with priority queues, first define
- a lock node.</p>
-<div class="note">
-<div class="label">Note</div>
-<div class="content">
-
-<p>There now exists a Lock implementation in ZooKeeper
- recipes directory. This is distributed with the release --
- src/recipes/lock directory of the release artifact.
- </p>
-
-</div>
-</div>
-<p>Clients wishing to obtain a lock do the following:</p>
-<ol>
-
-<li>
-
-<p>Call <strong>create( )</strong> with a pathname
- of "_locknode_/guid-lock-" and the <em>sequence</em> and
- <em>ephemeral</em> flags set. The <em>guid</em>
- is needed in case the create() result is missed. See the note below.</p>
-
-</li>
-
-
-<li>
-
-<p>Call <strong>getChildren( )</strong> on the lock
- node <em>without</em> setting the watch flag (this is
- important to avoid the herd effect).</p>
-
-</li>
-
-
-<li>
-
-<p>If the pathname created in step <strong>1</strong> has the lowest sequence number suffix, the
- client has the lock and the client exits the protocol.</p>
-
-</li>
-
-
-<li>
-
-<p>The client calls <strong>exists( )</strong> with
- the watch flag set on the path in the lock directory with the next
- lowest sequence number.</p>
-
-</li>
-
-
-<li>
-
-<p>if <strong>exists( )</strong> returns false, go
- to step <strong>2</strong>. Otherwise, wait for a
- notification for the pathname from the previous step before going to
- step <strong>2</strong>.</p>
-
-</li>
-
-</ol>
-<p>The unlock protocol is very simple: clients wishing to release a
- lock simply delete the node they created in step 1.</p>
-<p>Here are a few things to notice:</p>
-<ul>
-
-<li>
-
-<p>The removal of a node will only cause one client to wake up
- since each node is watched by exactly one client. In this way, you
- avoid the herd effect.</p>
-
-</li>
-
-</ul>
-<ul>
-
-<li>
-
-<p>There is no polling or timeouts.</p>
-
-</li>
-
-</ul>
-<ul>
-
-<li>
-
-<p>Because of the way you implement locking, it is easy to see the
- amount of lock contention, break locks, debug locking problems,
- etc.</p>
-
-</li>
-
-</ul>
-<a name="sc_recipes_GuidNote"></a>
-<h4>Recoverable Errors and the GUID</h4>
-<ul>
-
-<li>
-
-<p>If a recoverable error occurs calling <strong>create()</strong> the
- client should call <strong>getChildren()</strong> and check for a node
- containing the <em>guid</em> used in the path name.
- This handles the case (noted <a href="#sc_recipes_errorHandlingNote">above</a>) of
- the create() succeeding on the server but the server crashing before returning the name
- of the new node.</p>
-
-</li>
-
-</ul>
-<a name="Shared+Locks"></a>
-<h4>Shared Locks</h4>
-<p>You can implement shared locks by with a few changes to the lock
- protocol:</p>
-<table class="ForrestTable" cellspacing="1" cellpadding="4">
-
-
-<tr>
-
-<td><strong>Obtaining a read
- lock:</strong></td>
-
- <td><strong>Obtaining a write
- lock:</strong></td>
-
-</tr>
-
-
-<tr>
-
-<td>
-<ol>
-
-<li>
-
-<p>Call <strong>create( )</strong> to
- create a node with pathname
- "<span class="codefrag filename">guid-/read-</span>". This is the
- lock node use later in the protocol. Make sure to set both
- the <em>sequence</em> and
- <em>ephemeral</em> flags.</p>
-
-</li>
-
-
-<li>
-
-<p>Call <strong>getChildren( )</strong>
- on the lock node <em>without</em> setting the
- <em>watch</em> flag - this is important, as it
- avoids the herd effect.</p>
-
-</li>
-
-
-<li>
-
-<p>If there are no children with a pathname starting
- with "<span class="codefrag filename">write-</span>" and having a lower
- sequence number than the node created in step <strong>1</strong>, the client has the lock and can
- exit the protocol. </p>
-
-</li>
-
-
-<li>
-
-<p>Otherwise, call <strong>exists(
- )</strong>, with <em>watch</em> flag, set on
- the node in lock directory with pathname staring with
- "<span class="codefrag filename">write-</span>" having the next lowest
- sequence number.</p>
-
-</li>
-
-
-<li>
-
-<p>If <strong>exists( )</strong>
- returns <em>false</em>, goto step <strong>2</strong>.</p>
-
-</li>
-
-
-<li>
-
-<p>Otherwise, wait for a notification for the pathname
- from the previous step before going to step <strong>2</strong>
-</p>
-
-</li>
-
-</ol>
-</td>
-
- <td>
-<ol>
-
-<li>
-
-<p>Call <strong>create( )</strong> to
- create a node with pathname
- "<span class="codefrag filename">guid-/write-</span>". This is the
- lock node spoken of later in the protocol. Make sure to
- set both <em>sequence</em> and
- <em>ephemeral</em> flags.</p>
-
-</li>
-
-
-<li>
-
-<p>Call <strong>getChildren( )
- </strong> on the lock node <em>without</em>
- setting the <em>watch</em> flag - this is
- important, as it avoids the herd effect.</p>
-
-</li>
-
-
-<li>
-
-<p>If there are no children with a lower sequence
- number than the node created in step <strong>1</strong>, the client has the lock and the
- client exits the protocol.</p>
-
-</li>
-
-
-<li>
-
-<p>Call <strong>exists( ),</strong>
- with <em>watch</em> flag set, on the node with
- the pathname that has the next lowest sequence
- number.</p>
-
-</li>
-
-
-<li>
-
-<p>If <strong>exists( )</strong>
- returns <em>false</em>, goto step <strong>2</strong>. Otherwise, wait for a
- notification for the pathname from the previous step
- before going to step <strong>2</strong>.</p>
-
-</li>
-
-</ol>
-</td>
-
-</tr>
-
-
-</table>
-<p>Notes:</p>
-<ul>
-
-<li>
-
-<p>It might appear that this recipe creates a herd effect:
- when there is a large group of clients waiting for a read
- lock, and all getting notified more or less simultaneously
- when the "<span class="codefrag filename">write-</span>" node with the lowest
- sequence number is deleted. In fact. that's valid behavior:
- as all those waiting reader clients should be released since
- they have the lock. The herd effect refers to releasing a
- "herd" when in fact only a single or a small number of
- machines can proceed.</p>
-
-</li>
-
-</ul>
-<ul>
-
-<li>
-
-<p>See the <a href="#sc_recipes_GuidNote">note for Locks</a> on how to use the guid in the node.</p>
-
-</li>
-
-</ul>
-<a name="sc_revocableSharedLocks"></a>
-<h4>Revocable Shared Locks</h4>
-<p>With minor modifications to the Shared Lock protocol, you make
- shared locks revocable by modifying the shared lock protocol:</p>
-<p>In step <strong>1</strong>, of both obtain reader
- and writer lock protocols, call <strong>getData(
- )</strong> with <em>watch</em> set, immediately after the
- call to <strong>create( )</strong>. If the client
- subsequently receives notification for the node it created in step
- <strong>1</strong>, it does another <strong>getData( )</strong> on that node, with
- <em>watch</em> set and looks for the string "unlock", which
- signals to the client that it must release the lock. This is because,
- according to this shared lock protocol, you can request the client with
- the lock give up the lock by calling <strong>setData()
- </strong> on the lock node, writing "unlock" to that node.</p>
-<p>Note that this protocol requires the lock holder to consent to
- releasing the lock. Such consent is important, especially if the lock
- holder needs to do some processing before releasing the lock. Of course
- you can always implement <em>Revocable Shared Locks with Freaking
- Laser Beams</em> by stipulating in your protocol that the revoker
- is allowed to delete the lock node if after some length of time the lock
- isn't deleted by the lock holder.</p>
-<a name="sc_recipes_twoPhasedCommit"></a>
-<h3 class="h4">Two-phased Commit</h3>
-<p>A two-phase commit protocol is an algorithm that lets all clients in
- a distributed system agree either to commit a transaction or abort.</p>
-<p>In ZooKeeper, you can implement a two-phased commit by having a
- coordinator create a transaction node, say "/app/Tx", and one child node
- per participating site, say "/app/Tx/s_i". When coordinator creates the
- child node, it leaves the content undefined. Once each site involved in
- the transaction receives the transaction from the coordinator, the site
- reads each child node and sets a watch. Each site then processes the query
- and votes "commit" or "abort" by writing to its respective node. Once the
- write completes, the other sites are notified, and as soon as all sites
- have all votes, they can decide either "abort" or "commit". Note that a
- node can decide "abort" earlier if some site votes for "abort".</p>
-<p>An interesting aspect of this implementation is that the only role
- of the coordinator is to decide upon the group of sites, to create the
- ZooKeeper nodes, and to propagate the transaction to the corresponding
- sites. In fact, even propagating the transaction can be done through
- ZooKeeper by writing it in the transaction node.</p>
-<p>There are two important drawbacks of the approach described above.
- One is the message complexity, which is O(n²). The second is the
- impossibility of detecting failures of sites through ephemeral nodes. To
- detect the failure of a site using ephemeral nodes, it is necessary that
- the site create the node.</p>
-<p>To solve the first problem, you can have only the coordinator
- notified of changes to the transaction nodes, and then notify the sites
- once coordinator reaches a decision. Note that this approach is scalable,
- but it's is slower too, as it requires all communication to go through the
- coordinator.</p>
-<p>To address the second problem, you can have the coordinator
- propagate the transaction to the sites, and have each site creating its
- own ephemeral node.</p>
-<a name="sc_leaderElection"></a>
-<h3 class="h4">Leader Election</h3>
-<p>A simple way of doing leader election with ZooKeeper is to use the
- <strong>SEQUENCE|EPHEMERAL</strong> flags when creating
- znodes that represent "proposals" of clients. The idea is to have a znode,
- say "/election", such that each znode creates a child znode "/election/guid-n_"
- with both flags SEQUENCE|EPHEMERAL. With the sequence flag, ZooKeeper
- automatically appends a sequence number that is greater than any one
- previously appended to a child of "/election". The process that created
- the znode with the smallest appended sequence number is the leader.
- </p>
-<p>That's not all, though. It is important to watch for failures of the
- leader, so that a new client arises as the new leader in the case the
- current leader fails. A trivial solution is to have all application
- processes watching upon the current smallest znode, and checking if they
- are the new leader when the smallest znode goes away (note that the
- smallest znode will go away if the leader fails because the node is
- ephemeral). But this causes a herd effect: upon a failure of the current
- leader, all other processes receive a notification, and execute
- getChildren on "/election" to obtain the current list of children of
- "/election". If the number of clients is large, it causes a spike on the
- number of operations that ZooKeeper servers have to process. To avoid the
- herd effect, it is sufficient to watch for the next znode down on the
- sequence of znodes. If a client receives a notification that the znode it
- is watching is gone, then it becomes the new leader in the case that there
- is no smaller znode. Note that this avoids the herd effect by not having
- all clients watching the same znode. </p>
-<p>Here's the pseudo code:</p>
-<p>Let ELECTION be a path of choice of the application. To volunteer to
- be a leader: </p>
-<ol>
-
-<li>
-
-<p>Create znode z with path "ELECTION/guid-n_" with both SEQUENCE and
- EPHEMERAL flags;</p>
-
-</li>
-
-
-<li>
-
-<p>Let C be the children of "ELECTION", and i be the sequence
- number of z;</p>
-
-</li>
-
-
-<li>
-
-<p>Watch for changes on "ELECTION/guid-n_j", where j is the largest
- sequence number such that j < i and n_j is a znode in C;</p>
-
-</li>
-
-</ol>
-<p>Upon receiving a notification of znode deletion: </p>
-<ol>
-
-<li>
-
-<p>Let C be the new set of children of ELECTION; </p>
-
-</li>
-
-
-<li>
-
-<p>If z is the smallest node in C, then execute leader
- procedure;</p>
-
-</li>
-
-
-<li>
-
-<p>Otherwise, watch for changes on "ELECTION/guid-n_j", where j is the
- largest sequence number such that j < i and n_j is a znode in C;
- </p>
-
-</li>
-
-</ol>
-<p>Notes:</p>
-<ul>
-
-<li>
-
-<p>Note that the znode having no preceding znode on the list of
- children does not imply that the creator of this znode is aware that it is
- the current leader. Applications may consider creating a separate znode
- to acknowledge that the leader has executed the leader procedure. </p>
-
-</li>
-
-</ul>
-<ul>
-
-<li>
-
-<p>See the <a href="#sc_recipes_GuidNote">note for Locks</a> on how to use the guid in the node.</p>
-
-</li>
-
-</ul>
-</div>
-
-<p align="right">
-<font size="-2"></font>
-</p>
-</div>
-<!--+
- |end content
- +-->
-<div class="clearboth"> </div>
-</div>
-<div id="footer">
-<!--+
- |start bottomstrip
- +-->
-<div class="lastmodified">
-<script type="text/javascript"><!--
-document.write("Last Published: " + document.lastModified);
-// --></script>
-</div>
-<div class="copyright">
- Copyright ©
- <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
-</div>
-<!--+
- |end bottomstrip
- +-->
-</div>
-</body>
-</html>
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/recipes.pdf
----------------------------------------------------------------------
diff --git a/docs/recipes.pdf b/docs/recipes.pdf
deleted file mode 100644
index 5acb24f..0000000
Binary files a/docs/recipes.pdf and /dev/null differ
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/releasenotes.html
----------------------------------------------------------------------
diff --git a/docs/releasenotes.html b/docs/releasenotes.html
deleted file mode 100644
index 63a341a..0000000
--- a/docs/releasenotes.html
+++ /dev/null
@@ -1,1900 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.9">
-<meta name="Forrest-skin-name" content="pelt">
-<title>ZooKeeper 3.0.0 Release Notes</title>
-<link type="text/css" href="skin/basic.css" rel="stylesheet">
-<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
-<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
-<link type="text/css" href="skin/profile.css" rel="stylesheet">
-<script src="skin/getBlank.js" language="javascript" type="text/javascript"></script><script src="skin/getMenu.js" language="javascript" type="text/javascript"></script><script src="skin/fontsize.js" language="javascript" type="text/javascript"></script>
-<link rel="shortcut icon" href="images/favicon.ico">
-</head>
-<body onload="init()">
-<script type="text/javascript">ndeSetTextSize();</script>
-<div id="top">
-<!--+
- |breadtrail
- +-->
-<div class="breadtrail">
-<a href="http://www.apache.org/">Apache</a> > <a href="http://zookeeper.apache.org/">ZooKeeper</a> > <a href="http://zookeeper.apache.org/">ZooKeeper</a><script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script>
-</div>
-<!--+
- |header
- +-->
-<div class="header">
-<!--+
- |start group logo
- +-->
-<div class="grouplogo">
-<a href="http://hadoop.apache.org/"><img class="logoImage" alt="Hadoop" src="images/hadoop-logo.jpg" title="Apache Hadoop"></a>
-</div>
-<!--+
- |end group logo
- +-->
-<!--+
- |start Project Logo
- +-->
-<div class="projectlogo">
-<a href="http://zookeeper.apache.org/"><img class="logoImage" alt="ZooKeeper" src="images/zookeeper_small.gif" title="ZooKeeper: distributed coordination"></a>
-</div>
-<!--+
- |end Project Logo
- +-->
-<!--+
- |start Search
- +-->
-<div class="searchbox">
-<form action="http://www.google.com/search" method="get" class="roundtopsmall">
-<input value="zookeeper.apache.org" name="sitesearch" type="hidden"><input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google">
- <input name="Search" value="Search" type="submit">
-</form>
-</div>
-<!--+
- |end search
- +-->
-<!--+
- |start Tabs
- +-->
-<ul id="tabs">
-<li>
-<a class="unselected" href="http://zookeeper.apache.org/">Project</a>
-</li>
-<li>
-<a class="unselected" href="https://cwiki.apache.org/confluence/display/ZOOKEEPER/">Wiki</a>
-</li>
-<li class="current">
-<a class="selected" href="index.html">ZooKeeper 3.4 Documentation</a>
-</li>
-</ul>
-<!--+
- |end Tabs
- +-->
-</div>
-</div>
-<div id="main">
-<div id="publishedStrip">
-<!--+
- |start Subtabs
- +-->
-<div id="level2tabs"></div>
-<!--+
- |end Endtabs
- +-->
-<script type="text/javascript"><!--
-document.write("Last Published: " + document.lastModified);
-// --></script>
-</div>
-<!--+
- |breadtrail
- +-->
-<div class="breadtrail">
-
-
- </div>
-<!--+
- |start Menu, mainarea
- +-->
-<!--+
- |start Menu
- +-->
-<div id="menu">
-<div onclick="SwitchMenu('menu_selected_1.1', 'skin/')" id="menu_selected_1.1Title" class="menutitle" style="background-image: url('skin/images/chapter_open.gif');">Overview</div>
-<div id="menu_selected_1.1" class="selectedmenuitemgroup" style="display: block;">
-<div class="menuitem">
-<a href="index.html">Welcome</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperOver.html">Overview</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperStarted.html">Getting Started</a>
-</div>
-<div class="menupage">
-<div class="menupagetitle">Release Notes</div>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.2', 'skin/')" id="menu_1.2Title" class="menutitle">Developer</div>
-<div id="menu_1.2" class="menuitemgroup">
-<div class="menuitem">
-<a href="api/index.html">API Docs</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperProgrammers.html">Programmer's Guide</a>
-</div>
-<div class="menuitem">
-<a href="javaExample.html">Java Example</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperTutorial.html">Barrier and Queue Tutorial</a>
-</div>
-<div class="menuitem">
-<a href="recipes.html">Recipes</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.3', 'skin/')" id="menu_1.3Title" class="menutitle">Admin & Ops</div>
-<div id="menu_1.3" class="menuitemgroup">
-<div class="menuitem">
-<a href="zookeeperAdmin.html">Administrator's Guide</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperQuotas.html">Quota Guide</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperJMX.html">JMX</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperObservers.html">Observers Guide</a>
-</div>
-<div class="menuitem">
-<a href="zookeeperReconfig.html">Dynamic Reconfiguration</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.4', 'skin/')" id="menu_1.4Title" class="menutitle">Contributor</div>
-<div id="menu_1.4" class="menuitemgroup">
-<div class="menuitem">
-<a href="zookeeperInternals.html">ZooKeeper Internals</a>
-</div>
-</div>
-<div onclick="SwitchMenu('menu_1.5', 'skin/')" id="menu_1.5Title" class="menutitle">Miscellaneous</div>
-<div id="menu_1.5" class="menuitemgroup">
-<div class="menuitem">
-<a href="https://cwiki.apache.org/confluence/display/ZOOKEEPER">Wiki</a>
-</div>
-<div class="menuitem">
-<a href="https://cwiki.apache.org/confluence/display/ZOOKEEPER/FAQ">FAQ</a>
-</div>
-<div class="menuitem">
-<a href="http://zookeeper.apache.org/mailing_lists.html">Mailing Lists</a>
-</div>
-</div>
-<div id="credit"></div>
-<div id="roundbottom">
-<img style="display: none" class="corner" height="15" width="15" alt="" src="skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
-<!--+
- |alternative credits
- +-->
-<div id="credit2"></div>
-</div>
-<!--+
- |end Menu
- +-->
-<!--+
- |start content
- +-->
-<div id="content">
-<div title="Portable Document Format" class="pdflink">
-<a class="dida" href="releasenotes.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
- PDF</a>
-</div>
-<h1>ZooKeeper 3.0.0 Release Notes</h1>
-<div id="front-matter">
-<div id="minitoc-area">
-<ul class="minitoc">
-<li>
-<a href="#migration">Migration Instructions when Upgrading to 3.0.0</a>
-<ul class="minitoc">
-<li>
-<a href="#migration_code">Migrating Client Code</a>
-<ul class="minitoc">
-<li>
-<a href="#Watch+Management">Watch Management</a>
-</li>
-<li>
-<a href="#Java+API">Java API</a>
-</li>
-<li>
-<a href="#C+API">C API</a>
-</li>
-</ul>
-</li>
-<li>
-<a href="#migration_data">Migrating Server Data</a>
-</li>
-<li>
-<a href="#migration_config">Migrating Server Configuration</a>
-</li>
-</ul>
-</li>
-<li>
-<a href="#changes">Changes Since ZooKeeper 2.2.1</a>
-</li>
-</ul>
-</div>
-</div>
-
-
-
-
-
-<p>
-These release notes include new developer and user facing incompatibilities, features, and major improvements.
-</p>
-
-
-<ul>
-
-<li>
-<p>
-<a href="#migration">Migration Instructions</a>
-</p>
-</li>
-
-<li>
-<p>
-<a href="#changes">Changes</a>
-</p>
-</li>
-
-</ul>
-
-
-<a name="migration"></a>
-<h2 class="h3">Migration Instructions when Upgrading to 3.0.0</h2>
-<div class="section">
-<p>
-
-<em>You should only have to read this section if you are upgrading from a previous version of ZooKeeper to version 3.0.0, otw skip down to <a href="#changes">changes</a></em>
-
-</p>
-<p>
-A small number of changes in this release have resulted in non-backward compatible Zookeeper client user code and server instance data. The following instructions provide details on how to migrate code and date from version 2.2.1 to version 3.0.0.
-</p>
-<p>
-Note: ZooKeeper increments the major version number (major.minor.fix) when backward incompatible changes are made to the source base. As part of the migration from SourceForge we changed the package structure (com.yahoo.zookeeper.* to org.apache.zookeeper.*) and felt it was a good time to incorporate some changes that we had been withholding. As a result the following will be required when migrating from 2.2.1 to 3.0.0 version of ZooKeeper.
-</p>
-<ul>
-
-<li>
-<p>
-<a href="#migration_code">Migrating Client Code</a>
-</p>
-</li>
-
-<li>
-<p>
-<a href="#migration_data">Migrating Server Data</a>
-</p>
-</li>
-
-<li>
-<p>
-<a href="#migration_config">Migrating Server Configuration</a>
-</p>
-</li>
-
-</ul>
-<a name="migration_code"></a>
-<h3 class="h4">Migrating Client Code</h3>
-<p>
- The underlying client-server protocol has changed in version 3.0.0
- of ZooKeeper. As a result clients must be upgraded along with
- serving clusters to ensure proper operation of the system (old
- pre-3.0.0 clients are not guaranteed to operate against upgraded
- 3.0.0 servers and vice-versa).
-</p>
-<a name="Watch+Management"></a>
-<h4>Watch Management</h4>
-<p>
-In previous releases of ZooKeeper any watches registered by clients were lost if the client lost a connection to a ZooKeeper server.
-This meant that developers had to track watches they were interested in and reregister them if a session disconnect event was received.
-In this release the client library tracks watches that a client has registered and reregisters the watches when a connection is made to a new server.
-Applications that still manually reregister interest should continue working properly as long as they are able to handle unsolicited watches.
-For example, an old application may register a watch for /foo and /goo, lose the connection, and reregister only /goo.
-As long as the application is able to receive a notification for /foo, (probably ignoring it) it does not need to be changed.
-One caveat to the watch management: it is possible to miss an event for the creation and deletion of a znode if watching for creation and both the create and delete happens while the client is disconnected from ZooKeeper.
-</p>
-<p>
-This release also allows clients to specify call specific watch functions.
-This gives the developer the ability to modularize logic in different watch functions rather than cramming everything in the watch function attached to the ZooKeeper handle.
-Call specific watch functions receive all session events for as long as they are active, but will only receive the watch callbacks for which they are registered.
-</p>
-<a name="Java+API"></a>
-<h4>Java API</h4>
-<ol>
-
-<li>
-<p>The java package structure has changed from <strong>com.yahoo.zookeeper*</strong> to <strong>org.apache.zookeeper*</strong>. This will probably effect all of your java code which makes use of ZooKeeper APIs (typically import statements)</p>
-</li>
-
-<li>
-<p>A number of constants used in the client ZooKeeper API were re-specified using enums (rather than ints). See <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-7">ZOOKEEPER-7</a>, <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-132">ZOOKEEPER-132</a> and <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-139">ZOOKEEPER-139</a> for full details</p>
-</li>
-
-<li>
-<p>
-<a href="https://issues.apache.org/jira/browse/ZOOKEEPER-18">ZOOKEEPER-18</a> removed KeeperStateChanged, use KeeperStateDisconnected instead</p>
-</li>
-
-</ol>
-<p>
-Also see <a href="http://zookeeper.apache.org/docs/current/api/index.html">the current java API</a>
-
-</p>
-<a name="C+API"></a>
-<h4>C API</h4>
-<ol>
-
-<li>
-<p>A number of constants used in the client ZooKeeper API were renamed in order to reduce namespace collision, see <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-6">ZOOKEEPER-6</a> for full details</p>
-</li>
-
-</ol>
-<a name="migration_data"></a>
-<h3 class="h4">Migrating Server Data</h3>
-<p>
-The following issues resulted in changes to the on-disk data format (the snapshot and transaction log files contained within the ZK data directory) and require a migration utility to be run.
-</p>
-<ul>
-
-<li>
-<p>
-<a href="https://issues.apache.org/jira/browse/ZOOKEEPER-27">ZOOKEEPER-27 Unique DB identifiers for servers and clients</a>
-</p>
-</li>
-
-<li>
-<p>
-<a href="https://issues.apache.org/jira/browse/ZOOKEEPER-32">ZOOKEEPER-32 CRCs for ZooKeeper data</a>
-</p>
-</li>
-
-<li>
-<p>
-<a href="https://issues.apache.org/jira/browse/ZOOKEEPER-33">ZOOKEEPER-33 Better ACL management</a>
-</p>
-</li>
-
-<li>
-<p>
-<a href="https://issues.apache.org/jira/browse/ZOOKEEPER-38">ZOOKEEPER-38 headers (version+) in log/snap files</a>
-</p>
-</li>
-
-</ul>
-<p>
-
-<strong>The following must be run once, and only once, when upgrading the ZooKeeper server instances to version 3.0.0.</strong>
-
-</p>
-<div class="note">
-<div class="label">Note</div>
-<div class="content">
-
-<p>
- The <dataLogDir> and <dataDir> directories referenced
- below are specified by the <em>dataLogDir</em>
- and <em>dataDir</em> specification in your
- ZooKeeper config file
- respectively. <em>dataLogDir</em> defaults to the
- value of <em>dataDir</em> if not specified explicitly
- in the ZooKeeper server config file (in which case provide the
- same directory for both parameters to the upgrade utility).
- </p>
-
-</div>
-</div>
-<ol>
-
-<li>
-<p>Shutdown the ZooKeeper server cluster.</p>
-</li>
-
-<li>
-<p>Backup your <dataLogDir> and <dataDir> directories</p>
-</li>
-
-<li>
-<p>Run upgrade using</p>
-
-<ul>
-
-<li>
-<p>
-<span class="codefrag computeroutput">bin/zkServer.sh upgrade <dataLogDir> <dataDir></span>
-</p>
-</li>
-
-</ul>
-
-<p>or</p>
-
-<ul>
-
-<li>
-<p>
-<span class="codefrag computeroutput">java -classpath pathtolog4j:pathtozookeeper.jar UpgradeMain <dataLogDir> <dataDir></span>
-</p>
-</li>
-
-</ul>
-
-<p>where <dataLogDir> is the directory where all transaction logs (log.*) are stored. <dataDir> is the directory where all the snapshots (snapshot.*) are stored.</p>
-
-</li>
-
-<li>
-<p>Restart the cluster. </p>
-</li>
-
-</ol>
-<p>
- If you have any failure during the upgrade procedure keep reading to sanitize your database.
- </p>
-<p>This is how upgrade works in ZooKeeper. This will help you troubleshoot in case you have problems while upgrading</p>
-<ol>
-
-<li>
-<p>Upgrade moves files from <dataLogDir> and <dataDir> to <dataLogDir>/version-1/ and <dataDir>/version-1 respectively (version-1 sub-directory is created by the upgrade utility). </p>
-</li>
-
-<li>
-<p>Upgrade creates a new version sub-directory <dataDir>/version-2 and <dataLogDir>/version-2</p>
-</li>
-
-<li>
-<p>Upgrade reads the old database from <dataDir>/version-1 and <dataLogDir>/version-1 into the memory and creates a new upgraded snapshot. </p>
-</li>
-
-<li>
-<p>Upgrade writes the new database in <dataDir>/version-2. </p>
-</li>
-
-</ol>
-<p>Troubleshooting.</p>
-<ol>
-
-<li>
-<p>In case you start ZooKeeper 3.0 without upgrading from 2.0 on a 2.0 database - the servers will start up with an empty database.
- This is because the servers assume that <dataDir>/version-2 and <dataLogDir>/version-2 will have the database to start with. Since this will be empty
- in case of no upgrade, the servers will start with an empty database. In such a case, shutdown the ZooKeeper servers, remove the version-2 directory (remember
- this will lead to loss of updates after you started 3.0.)
- and then start the upgrade procedure.</p>
-</li>
-
-<li>
-<p>If the upgrade fails while trying to rename files into the version-1 directory, you should try and move all the files under <dataDir>/version-1
- and <dataLogDir>/version-1 to <dataDir> and <dataLogDir> respectively. Then try upgrade again.
- </p>
-
-</li>
-
-<li>
-<p> If you do not wish to run with ZooKeeper 3.0 and prefer to run with ZooKeeper 2.0 and have already upgraded - you can run ZooKeeper 2 with
- the <dataDir> and <dataLogDir> directories changed to <dataDir>/version-1 and <dataLogDir>/version-1. Remember that you will lose all the updates that you made after the upgrade.
-</p>
-</li>
-
-</ol>
-<a name="migration_config"></a>
-<h3 class="h4">Migrating Server Configuration</h3>
-<p>
-There is a significant change to the ZooKeeper server configuration file.
-</p>
-<p>The default election algorithm, specified by
- the <em>electionAlg</em> configuration attribute, has
- changed from a default of <em>0</em> to a default
- of <em>3</em>. See
- <a href="zookeeperAdmin.html#sc_clusterOptions">Cluster
- Options</a> section of the administrators guide, specifically
- the <em>electionAlg</em>
- and <em>server.X</em> properties.
-</p>
-<p>
- You will either need to explicitly
- set <em>electionAlg</em> to it's previous default value
- of <em>0</em> or change
- your <em>server.X</em> options to include the leader
- election port.
-</p>
-</div>
-
-
-<a name="changes"></a>
-<h2 class="h3">Changes Since ZooKeeper 2.2.1</h2>
-<div class="section">
-<p>
-Version 2.2.1 code, documentation, binaries, etc... are still accessible on <a href="http://sourceforge.net/projects/zookeeper">SourceForge</a>
-
-</p>
-<table class="ForrestTable" cellspacing="1" cellpadding="4">
-<caption>Changes Since ZooKeeper 2.2.1</caption>
-
-<title>Changes Since ZooKeeper 2.2.1</title>
-
-
-<tr>
-
-<th>Issue</th>
- <th>Notes</th>
-
-</tr>
-
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-43">
- ZOOKEEPER-43</a>
- </td>
- <td>
- Server side of auto reset watches.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-132">
- ZOOKEEPER-132</a>
- </td>
- <td>
- Create Enum to replace CreateFlag in ZooKepper.create method
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-139">
- ZOOKEEPER-139</a>
- </td>
- <td>
- Create Enums for WatcherEvent's KeeperState and EventType
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-18">
- ZOOKEEPER-18</a>
- </td>
- <td>
- keeper state inconsistency
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-38">
- ZOOKEEPER-38</a>
- </td>
- <td>
- headers in log/snap files
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-8">
- ZOOKEEPER-8</a>
- </td>
- <td>
- Stat enchaned to include num of children and size
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-6">
- ZOOKEEPER-6</a>
- </td>
- <td>
- List of problem identifiers in zookeeper.h
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-7">
- ZOOKEEPER-7</a>
- </td>
- <td>
- Use enums rather than ints for types and state
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-27">
- ZOOKEEPER-27</a>
- </td>
- <td>
- Unique DB identifiers for servers and clients
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-32">
- ZOOKEEPER-32</a>
- </td>
- <td>
- CRCs for ZooKeeper data
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-33">
- ZOOKEEPER-33</a>
- </td>
- <td>
- Better ACL management
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-203">
- ZOOKEEPER-203</a>
- </td>
- <td>
- fix datadir typo in releasenotes
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-145">
- ZOOKEEPER-145</a>
- </td>
- <td>
- write detailed release notes for users migrating from 2.x to 3.0
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-23">
- ZOOKEEPER-23</a>
- </td>
- <td>
- Auto reset of watches on reconnect
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-191">
- ZOOKEEPER-191</a>
- </td>
- <td>
- forrest docs for upgrade.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-201">
- ZOOKEEPER-201</a>
- </td>
- <td>
- validate magic number when reading snapshot and transaction logs
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-200">
- ZOOKEEPER-200</a>
- </td>
- <td>
- the magic number for snapshot and log must be different
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-199">
- ZOOKEEPER-199</a>
- </td>
- <td>
- fix log messages in persistence code
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-197">
- ZOOKEEPER-197</a>
- </td>
- <td>
- create checksums for snapshots
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-198">
- ZOOKEEPER-198</a>
- </td>
- <td>
- apache license header missing from FollowerSyncRequest.java
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-5">
- ZOOKEEPER-5</a>
- </td>
- <td>
- Upgrade Feature in Zookeeper server.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-194">
- ZOOKEEPER-194</a>
- </td>
- <td>
- Fix terminology in zookeeperAdmin.xml
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-151">
- ZOOKEEPER-151</a>
- </td>
- <td>
- Document change to server configuration
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-193">
- ZOOKEEPER-193</a>
- </td>
- <td>
- update java example doc to compile with latest zookeeper
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-187">
- ZOOKEEPER-187</a>
- </td>
- <td>
- CreateMode api docs missing
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-186">
- ZOOKEEPER-186</a>
- </td>
- <td>
- add new "releasenotes.xml" to forrest documentation
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-190">
- ZOOKEEPER-190</a>
- </td>
- <td>
- Reorg links to docs and navs to docs into related sections
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-189">
- ZOOKEEPER-189</a>
- </td>
- <td>
- forrest build not validated xml of input documents
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-188">
- ZOOKEEPER-188</a>
- </td>
- <td>
- Check that election port is present for all servers
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-185">
- ZOOKEEPER-185</a>
- </td>
- <td>
- Improved version of FLETest
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-184">
- ZOOKEEPER-184</a>
- </td>
- <td>
- tests: An explicit include derective is needed for the usage of memcpy functions
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-183">
- ZOOKEEPER-183</a>
- </td>
- <td>
- Array subscript is above array bounds in od_completion, src/cli.c.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-182">
- ZOOKEEPER-182</a>
- </td>
- <td>
- zookeeper_init accepts empty host-port string and returns valid pointer to zhandle_t.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-17">
- ZOOKEEPER-17</a>
- </td>
- <td>
- zookeeper_init doc needs clarification
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-181">
- ZOOKEEPER-181</a>
- </td>
- <td>
- Some Source Forge Documents did not get moved over: javaExample, zookeeperTutorial, zookeeperInternals
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-180">
- ZOOKEEPER-180</a>
- </td>
- <td>
- Placeholder sections needed in document for new topics that the umbrella jira discusses
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-179">
- ZOOKEEPER-179</a>
- </td>
- <td>
- Programmer's Guide "Basic Operations" section is missing content
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-178">
- ZOOKEEPER-178</a>
- </td>
- <td>
- FLE test.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-159">
- ZOOKEEPER-159</a>
- </td>
- <td>
- Cover two corner cases of leader election
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-156">
- ZOOKEEPER-156</a>
- </td>
- <td>
- update programmer guide with acl details from old wiki page
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-154">
- ZOOKEEPER-154</a>
- </td>
- <td>
- reliability graph diagram in overview doc needs context
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-157">
- ZOOKEEPER-157</a>
- </td>
- <td>
- Peer can't find existing leader
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-155">
- ZOOKEEPER-155</a>
- </td>
- <td>
- improve "the zookeeper project" section of overview doc
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-140">
- ZOOKEEPER-140</a>
- </td>
- <td>
- Deadlock in QuorumCnxManager
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-147">
- ZOOKEEPER-147</a>
- </td>
- <td>
- This is version of the documents with most of the [tbd...] scrubbed out
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-150">
- ZOOKEEPER-150</a>
- </td>
- <td>
- zookeeper build broken
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-136">
- ZOOKEEPER-136</a>
- </td>
- <td>
- sync causes hang in all followers of quorum.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-134">
- ZOOKEEPER-134</a>
- </td>
- <td>
- findbugs cleanup
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-133">
- ZOOKEEPER-133</a>
- </td>
- <td>
- hudson tests failing intermittently
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-144">
- ZOOKEEPER-144</a>
- </td>
- <td>
- add tostring support for watcher event, and enums for event type/state
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-21">
- ZOOKEEPER-21</a>
- </td>
- <td>
- Improve zk ctor/watcher
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-142">
- ZOOKEEPER-142</a>
- </td>
- <td>
- Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-93">
- ZOOKEEPER-93</a>
- </td>
- <td>
- Create Documentation for Zookeeper
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-117">
- ZOOKEEPER-117</a>
- </td>
- <td>
- threading issues in Leader election
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-137">
- ZOOKEEPER-137</a>
- </td>
- <td>
- client watcher objects can lose events
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-131">
- ZOOKEEPER-131</a>
- </td>
- <td>
- Old leader election can elect a dead leader over and over again
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-130">
- ZOOKEEPER-130</a>
- </td>
- <td>
- update build.xml to support apache release process
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-118">
- ZOOKEEPER-118</a>
- </td>
- <td>
- findbugs flagged switch statement in followerrequestprocessor.run
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-115">
- ZOOKEEPER-115</a>
- </td>
- <td>
- Potential NPE in QuorumCnxManager
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-114">
- ZOOKEEPER-114</a>
- </td>
- <td>
- cleanup ugly event messages in zookeeper client
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-112">
- ZOOKEEPER-112</a>
- </td>
- <td>
- src/java/main ZooKeeper.java has test code embedded into it.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-39">
- ZOOKEEPER-39</a>
- </td>
- <td>
- Use Watcher objects rather than boolean on read operations.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-97">
- ZOOKEEPER-97</a>
- </td>
- <td>
- supports optional output directory in code generator.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-101">
- ZOOKEEPER-101</a>
- </td>
- <td>
- Integrate ZooKeeper with "violations" feature on hudson
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-105">
- ZOOKEEPER-105</a>
- </td>
- <td>
- Catch Zookeeper exceptions and print on the stderr.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-42">
- ZOOKEEPER-42</a>
- </td>
- <td>
- Change Leader Election to fast tcp.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-48">
- ZOOKEEPER-48</a>
- </td>
- <td>
- auth_id now handled correctly when no auth ids present
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-44">
- ZOOKEEPER-44</a>
- </td>
- <td>
- Create sequence flag children with prefixes of 0's so that they can be lexicographically sorted.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-108">
- ZOOKEEPER-108</a>
- </td>
- <td>
- Fix sync operation reordering on a Quorum.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-25">
- ZOOKEEPER-25</a>
- </td>
- <td>
- Fuse module for Zookeeper.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-58">
- ZOOKEEPER-58</a>
- </td>
- <td>
- Race condition on ClientCnxn.java
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-56">
- ZOOKEEPER-56</a>
- </td>
- <td>
- Add clover support to build.xml.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-75">
- ZOOKEEPER-75</a>
- </td>
- <td>
- register the ZooKeeper mailing lists with nabble.com
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-54">
- ZOOKEEPER-54</a>
- </td>
- <td>
- remove sleeps in the tests.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-55">
- ZOOKEEPER-55</a>
- </td>
- <td>
- build.xml failes to retrieve a release number from SVN and the ant target "dist" fails
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-89">
- ZOOKEEPER-89</a>
- </td>
- <td>
- invoke WhenOwnerListener.whenNotOwner when the ZK connection fails
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-90">
- ZOOKEEPER-90</a>
- </td>
- <td>
- invoke WhenOwnerListener.whenNotOwner when the ZK session expires and the znode is the leader
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-82">
- ZOOKEEPER-82</a>
- </td>
- <td>
- Make the ZooKeeperServer more DI friendly.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-110">
- ZOOKEEPER-110</a>
- </td>
- <td>
- Build script relies on svnant, which is not compatible with subversion 1.5 working copies
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-111">
- ZOOKEEPER-111</a>
- </td>
- <td>
- Significant cleanup of existing tests.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-122">
- ZOOKEEPER-122</a>
- </td>
- <td>
- Fix NPE in jute's Utils.toCSVString.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-123">
- ZOOKEEPER-123</a>
- </td>
- <td>
- Fix the wrong class is specified for the logger.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-2">
- ZOOKEEPER-2</a>
- </td>
- <td>
- Fix synchronization issues in QuorumPeer and FastLeader election.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-125">
- ZOOKEEPER-125</a>
- </td>
- <td>
- Remove unwanted class declaration in FastLeaderElection.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-61">
- ZOOKEEPER-61</a>
- </td>
- <td>
- Address in client/server test cases.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-75">
- ZOOKEEPER-75</a>
- </td>
- <td>
- cleanup the library directory
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-109">
- ZOOKEEPER-109</a>
- </td>
- <td>
- cleanup of NPE and Resource issue nits found by static analysis
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-76">
- ZOOKEEPER-76</a>
- </td>
- <td>
- Commit 677109 removed the cobertura library, but not the build targets.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-63">
- ZOOKEEPER-63</a>
- </td>
- <td>
- Race condition in client close
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-70">
- ZOOKEEPER-70</a>
- </td>
- <td>
- Add skeleton forrest doc structure for ZooKeeper
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-79">
- ZOOKEEPER-79</a>
- </td>
- <td>
- Document jacob's leader election on the wiki recipes page
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-73">
- ZOOKEEPER-73</a>
- </td>
- <td>
- Move ZK wiki from SourceForge to Apache
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-72">
- ZOOKEEPER-72</a>
- </td>
- <td>
- Initial creation/setup of ZooKeeper ASF site.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-71">
- ZOOKEEPER-71</a>
- </td>
- <td>
- Determine what to do re ZooKeeper Changelog
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-68">
- ZOOKEEPER-68</a>
- </td>
- <td>
- parseACLs in ZooKeeper.java fails to parse elements of ACL, should be lastIndexOf rather than IndexOf
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-130">
- ZOOKEEPER-130</a>
- </td>
- <td>
- update build.xml to support apache release process.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-131">
- ZOOKEEPER-131</a>
- </td>
- <td>
- Fix Old leader election can elect a dead leader over and over again.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-137">
- ZOOKEEPER-137</a>
- </td>
- <td>
- client watcher objects can lose events
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-117">
- ZOOKEEPER-117</a>
- </td>
- <td>
- threading issues in Leader election
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-128">
- ZOOKEEPER-128</a>
- </td>
- <td>
- test coverage on async client operations needs to be improved
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-127">
- ZOOKEEPER-127</a>
- </td>
- <td>
- Use of non-standard election ports in config breaks services
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-53">
- ZOOKEEPER-53</a>
- </td>
- <td>
- tests failing on solaris.
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-172">
- ZOOKEEPER-172</a>
- </td>
- <td>
- FLE Test
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-41">
- ZOOKEEPER-41</a>
- </td>
- <td>
- Sample startup script
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-33">
- ZOOKEEPER-33</a>
- </td>
- <td>
- Better ACL management
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-49">
- ZOOKEEPER-49</a>
- </td>
- <td>
- SetACL does not work
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-20">
- ZOOKEEPER-20</a>
- </td>
- <td>
- Child watches are not triggered when the node is deleted
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-15">
- ZOOKEEPER-15</a>
- </td>
- <td>
- handle failure better in build.xml:test
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-11">
- ZOOKEEPER-11</a>
- </td>
- <td>
- ArrayList is used instead of List
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-45">
- ZOOKEEPER-45</a>
- </td>
- <td>
- Restructure the SVN repository after initial import
- </td>
-
-</tr>
-
-<tr>
-
-<td>
- <a href="https://issues.apache.org/jira/browse/ZOOKEEPER-1">
- ZOOKEEPER-1</a>
- </td>
- <td>
- Initial ZooKeeper code contribution from Yahoo!
- </td>
-
-</tr>
-
-
-</table>
-</div>
-
-<p align="right">
-<font size="-2"></font>
-</p>
-</div>
-<!--+
- |end content
- +-->
-<div class="clearboth"> </div>
-</div>
-<div id="footer">
-<!--+
- |start bottomstrip
- +-->
-<div class="lastmodified">
-<script type="text/javascript"><!--
-document.write("Last Published: " + document.lastModified);
-// --></script>
-</div>
-<div class="copyright">
- Copyright ©
- 2008-2013 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
-</div>
-<!--+
- |end bottomstrip
- +-->
-</div>
-</body>
-</html>
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/releasenotes.pdf
----------------------------------------------------------------------
diff --git a/docs/releasenotes.pdf b/docs/releasenotes.pdf
deleted file mode 100644
index 8a40bbe..0000000
Binary files a/docs/releasenotes.pdf and /dev/null differ
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/skin/CommonMessages_de.xml
----------------------------------------------------------------------
diff --git a/docs/skin/CommonMessages_de.xml b/docs/skin/CommonMessages_de.xml
deleted file mode 100644
index bc46119..0000000
--- a/docs/skin/CommonMessages_de.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<catalogue>
- <message key="Font size:">Schriftgr�sse:</message>
- <message key="Last Published:">Zuletzt ver�ffentlicht:</message>
- <message key="Search">Suche:</message>
- <message key="Search the site with">Suche auf der Seite mit</message>
-</catalogue>
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/skin/CommonMessages_en_US.xml
----------------------------------------------------------------------
diff --git a/docs/skin/CommonMessages_en_US.xml b/docs/skin/CommonMessages_en_US.xml
deleted file mode 100644
index 88dfe14..0000000
--- a/docs/skin/CommonMessages_en_US.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<catalogue>
- <message key="Font size:">Font size:</message>
- <message key="Last Published:">Last Published:</message>
- <message key="Search">Search</message>
- <message key="Search the site with">Search site with</message>
-</catalogue>
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/skin/CommonMessages_es.xml
----------------------------------------------------------------------
diff --git a/docs/skin/CommonMessages_es.xml b/docs/skin/CommonMessages_es.xml
deleted file mode 100644
index 63be671..0000000
--- a/docs/skin/CommonMessages_es.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<catalogue>
- <message key="Font size:">Tama�o del texto:</message>
- <message key="Last Published:">Fecha de publicaci�n:</message>
- <message key="Search">Buscar</message>
- <message key="Search the site with">Buscar en</message>
-</catalogue>
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/skin/CommonMessages_fr.xml
----------------------------------------------------------------------
diff --git a/docs/skin/CommonMessages_fr.xml b/docs/skin/CommonMessages_fr.xml
deleted file mode 100644
index 622569a..0000000
--- a/docs/skin/CommonMessages_fr.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements. See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
--->
-<catalogue>
- <message key="Font size:">Taille :</message>
- <message key="Last Published:">Derni�re publication :</message>
- <message key="Search">Rechercher</message>
- <message key="Search the site with">Rechercher sur le site avec</message>
-</catalogue>
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/skin/basic.css
----------------------------------------------------------------------
diff --git a/docs/skin/basic.css b/docs/skin/basic.css
deleted file mode 100644
index 01c383d..0000000
--- a/docs/skin/basic.css
+++ /dev/null
@@ -1,167 +0,0 @@
-/*
-* Licensed to the Apache Software Foundation (ASF) under one or more
-* contributor license agreements. See the NOTICE file distributed with
-* this work for additional information regarding copyright ownership.
-* The ASF licenses this file to You under the Apache License, Version 2.0
-* (the "License"); you may not use this file except in compliance with
-* the License. You may obtain a copy of the License at
-*
-* http://www.apache.org/licenses/LICENSE-2.0
-*
-* Unless required by applicable law or agreed to in writing, software
-* distributed under the License is distributed on an "AS IS" BASIS,
-* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-* See the License for the specific language governing permissions and
-* limitations under the License.
-*/
-/**
- * General
- */
-
-img { border: 0; }
-
-#content table {
- border: 0;
- width: 100%;
-}
-/*Hack to get IE to render the table at 100%*/
-* html #content table { margin-left: -3px; }
-
-#content th,
-#content td {
- margin: 0;
- padding: 0;
- vertical-align: top;
-}
-
-.clearboth {
- clear: both;
-}
-
-.note, .warning, .fixme {
- clear:right;
- border: solid black 1px;
- margin: 1em 3em;
-}
-
-.note .label {
- background: #369;
- color: white;
- font-weight: bold;
- padding: 5px 10px;
-}
-.note .content {
- background: #F0F0FF;
- color: black;
- line-height: 120%;
- font-size: 90%;
- padding: 5px 10px;
-}
-.warning .label {
- background: #C00;
- color: white;
- font-weight: bold;
- padding: 5px 10px;
-}
-.warning .content {
- background: #FFF0F0;
- color: black;
- line-height: 120%;
- font-size: 90%;
- padding: 5px 10px;
-}
-.fixme .label {
- background: #C6C600;
- color: black;
- font-weight: bold;
- padding: 5px 10px;
-}
-.fixme .content {
- padding: 5px 10px;
-}
-
-/**
- * Typography
- */
-
-body {
- font-family: verdana, "Trebuchet MS", arial, helvetica, sans-serif;
- font-size: 100%;
-}
-
-#content {
- font-family: Georgia, Palatino, Times, serif;
- font-size: 95%;
-}
-#tabs {
- font-size: 70%;
-}
-#menu {
- font-size: 80%;
-}
-#footer {
- font-size: 70%;
-}
-
-h1, h2, h3, h4, h5, h6 {
- font-family: "Trebuchet MS", verdana, arial, helvetica, sans-serif;
- font-weight: bold;
- margin-top: 1em;
- margin-bottom: .5em;
-}
-
-h1 {
- margin-top: 0;
- margin-bottom: 1em;
- font-size: 1.4em;
-}
-#content h1 {
- font-size: 160%;
- margin-bottom: .5em;
-}
-#menu h1 {
- margin: 0;
- padding: 10px;
- background: #336699;
- color: white;
-}
-h2 { font-size: 120%; }
-h3 { font-size: 100%; }
-h4 { font-size: 90%; }
-h5 { font-size: 80%; }
-h6 { font-size: 75%; }
-
-p {
- line-height: 120%;
- text-align: left;
- margin-top: .5em;
- margin-bottom: 1em;
-}
-
-#content li,
-#content th,
-#content td,
-#content li ul,
-#content li ol{
- margin-top: .5em;
- margin-bottom: .5em;
-}
-
-
-#content li li,
-#minitoc-area li{
- margin-top: 0em;
- margin-bottom: 0em;
-}
-
-#content .attribution {
- text-align: right;
- font-style: italic;
- font-size: 85%;
- margin-top: 1em;
-}
-
-.codefrag {
- font-family: "Courier New", Courier, monospace;
- font-size: 110%;
-}
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/zookeeper/blob/e5fc1228/docs/skin/breadcrumbs-optimized.js
----------------------------------------------------------------------
diff --git a/docs/skin/breadcrumbs-optimized.js b/docs/skin/breadcrumbs-optimized.js
deleted file mode 100644
index 507612a..0000000
--- a/docs/skin/breadcrumbs-optimized.js
+++ /dev/null
@@ -1,90 +0,0 @@
-/*
-* Licensed to the Apache Software Foundation (ASF) under one or more
-* contributor license agreements. See the NOTICE file distributed with
-* this work for additional information regarding copyright ownership.
-* The ASF licenses this file to You under the Apache License, Version 2.0
-* (the "License"); you may not use this file except in compliance with
-* the License. You may obtain a copy of the License at
-*
-* http://www.apache.org/licenses/LICENSE-2.0
-*
-* Unless required by applicable law or agreed to in writing, software
-* distributed under the License is distributed on an "AS IS" BASIS,
-* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-* See the License for the specific language governing permissions and
-* limitations under the License.
-*/
-var PREPREND_CRUMBS=new Array();
-var link1="@skinconfig.trail.link1.name@";
-var link2="@skinconfig.trail.link2.name@";
-var link3="@skinconfig.trail.link3.name@";
-if(!(link1=="")&&!link1.indexOf( "@" ) == 0){
- PREPREND_CRUMBS.push( new Array( link1, @skinconfig.trail.link1.href@ ) ); }
-if(!(link2=="")&&!link2.indexOf( "@" ) == 0){
- PREPREND_CRUMBS.push( new Array( link2, @skinconfig.trail.link2.href@ ) ); }
-if(!(link3=="")&&!link3.indexOf( "@" ) == 0){
- PREPREND_CRUMBS.push( new Array( link3, @skinconfig.trail.link3.href@ ) ); }
-var DISPLAY_SEPARATOR=" > ";
-var DISPLAY_PREPREND=" > ";
-var DISPLAY_POSTPREND=":";
-var CSS_CLASS_CRUMB="breadcrumb";
-var CSS_CLASS_TRAIL="breadcrumbTrail";
-var CSS_CLASS_SEPARATOR="crumbSeparator";
-var FILE_EXTENSIONS=new Array( ".html", ".htm", ".jsp", ".php", ".php3", ".php4" );
-var PATH_SEPARATOR="/";
-
-function sc(s) {
- var l=s.toLowerCase();
- return l.substr(0,1).toUpperCase()+l.substr(1);
-}
-function getdirs() {
- var t=document.location.pathname.split(PATH_SEPARATOR);
- var lc=t[t.length-1];
- for(var i=0;i < FILE_EXTENSIONS.length;i++)
- {
- if(lc.indexOf(FILE_EXTENSIONS[i]))
- return t.slice(1,t.length-1); }
- return t.slice(1,t.length);
-}
-function getcrumbs( d )
-{
- var pre = "/";
- var post = "/";
- var c = new Array();
- if( d != null )
- {
- for(var i=0;i < d.length;i++) {
- pre+=d[i]+postfix;
- c.push(new Array(d[i],pre)); }
- }
- if(PREPREND_CRUMBS.length > 0 )
- return PREPREND_CRUMBS.concat( c );
- return c;
-}
-function gettrail( c )
-{
- var h=DISPLAY_PREPREND;
- for(var i=0;i < c.length;i++)
- {
- h+='<a href="'+c[i][1]+'" >'+sc(c[i][0])+'</a>';
- if(i!=(c.length-1))
- h+=DISPLAY_SEPARATOR; }
- return h+DISPLAY_POSTPREND;
-}
-
-function gettrailXHTML( c )
-{
- var h='<span class="'+CSS_CLASS_TRAIL+'">'+DISPLAY_PREPREND;
- for(var i=0;i < c.length;i++)
- {
- h+='<a href="'+c[i][1]+'" class="'+CSS_CLASS_CRUMB+'">'+sc(c[i][0])+'</a>';
- if(i!=(c.length-1))
- h+='<span class="'+CSS_CLASS_SEPARATOR+'">'+DISPLAY_SEPARATOR+'</span>'; }
- return h+DISPLAY_POSTPREND+'</span>';
-}
-
-if(document.location.href.toLowerCase().indexOf("http://")==-1)
- document.write(gettrail(getcrumbs()));
-else
- document.write(gettrail(getcrumbs(getdirs())));
-