Files
deb-kazoo/docs/async_usage.rst
Joshua Harlow df067e974c Add new eventlet docs + a few other tweaks to the index.rst
Explain what the new eventlet handler is and how it can be
used (with api docs as well) and links some of the items in
index.rst to targets (and makes the irc link clickable).
2015-02-13 12:32:39 -08:00

3.6 KiB

Asynchronous Usage

The asynchronous Kazoo API relies on the ~kazoo.interfaces.IAsyncResult object which is returned by all the asynchronous methods. Callbacks can be added with the ~kazoo.interfaces.IAsyncResult.rawlink method which works in a consistent manner whether threads or an asynchronous framework like gevent is used.

Kazoo utilizes a pluggable ~kazoo.interfaces.IHandler interface which abstracts the callback system to ensure it works consistently.

Connection Handling

Creating a connection:

from kazoo.client import KazooClient
from kazoo.handlers.gevent import SequentialGeventHandler

zk = KazooClient(handler=SequentialGeventHandler())

# returns immediately
event = zk.start_async()

# Wait for 30 seconds and see if we're connected
event.wait(timeout=30)

if not zk.connected:
    # Not connected, stop trying to connect
    zk.stop()
    raise Exception("Unable to connect.")

In this example, the wait method is used on the event object returned by the ~kazoo.client.KazooClient.start_async method. A timeout is always used because its possible that we might never connect and that should be handled gracefully.

The ~kazoo.handlers.gevent.SequentialGeventHandler is used when you want to use gevent (and ~kazoo.handlers.eventlet.SequentialEventletHandler when eventlet is used). Kazoo doesn't rely on gevents/eventlet monkey patching and requires that you pass in the appropriate handler, the default handler is ~kazoo.handlers.threading.SequentialThreadingHandler.

Asynchronous Callbacks

All kazoo _async methods except for ~kazoo.client.KazooClient.start_async return an ~kazoo.interfaces.IAsyncResult instance. These instances allow you to see when a result is ready, or chain one or more callback functions to the result that will be called when it's ready.

The callback function will be passed the ~kazoo.interfaces.IAsyncResult instance and should call the ~kazoo.interfaces.IAsyncResult.get method on it to retrieve the value. This call could result in an exception being raised if the asynchronous function encountered an error. It should be caught and handled appropriately.

Example:

import sys

from kazoo.exceptions import ConnectionLossException
from kazoo.exceptions import NoAuthException

def my_callback(async_obj):
    try:
        children = async_obj.get()
        do_something(children)
    except (ConnectionLossException, NoAuthException):
        sys.exit(1)

# Both these statements return immediately, the second sets a callback
# that will be run when get_children_async has its return value
async_obj = zk.get_children_async("/some/node")
async_obj.rawlink(my_callback)

Zookeeper CRUD

The following CRUD methods all work the same as their synchronous counterparts except that they return an ~kazoo.interfaces.IAsyncResult object.

Creating Method:

  • ~kazoo.client.KazooClient.create_async

Reading Methods:

  • ~kazoo.client.KazooClient.exists_async
  • ~kazoo.client.KazooClient.get_async
  • ~kazoo.client.KazooClient.get_children_async

Updating Methods:

  • ~kazoo.client.KazooClient.set_async

Deleting Methods:

  • ~kazoo.client.KazooClient.delete_async

The ~kazoo.client.KazooClient.ensure_path has no asynchronous counterpart at the moment nor can the ~kazoo.client.KazooClient.delete_async method do recursive deletes.