Distributed Coordination with Python
Upcoming SlideShare
Loading in...5
×
 

Distributed Coordination with Python

on

  • 1,179 views

This talk covers why Apache Zookeeper is a good fit for coordinating processes in a distributed environment, prior Python attempts at a client and the current state of the art Python client library, ...

This talk covers why Apache Zookeeper is a good fit for coordinating processes in a distributed environment, prior Python attempts at a client and the current state of the art Python client library, how unifying development efforts to merge several Python client libraries has paid off, features available to Python processes, and how to gracefully handle failures in a set of distributed processes.

Statistics

Views

Total Views
1,179
Views on SlideShare
1,154
Embed Views
25

Actions

Likes
4
Downloads
19
Comments
0

2 Embeds 25

http://lanyrd.com 13
https://twitter.com 12

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Distributed Coordination with Python Distributed Coordination with Python Presentation Transcript

  • DISTRIBUTED COORDINATION WITH PYTHON BenBangert mozilla
  • Toolsof theTrade
  • DISTRIBUTED COORDINATION IS NOT... • Distributed Databases (Cassandra, Riak) • Distributed Computing (Hadoop, etc.) • Distributed Event Analysis (Storm)
  • TheCommonElement
  • Apache Zookeeper
  • ZooKeeperisacentralizedservicefor maintainingconfigurationinformation, naming,providingdistributedsynchronization, andprovidinggroupservices.
  • ZOOKEEPER
  • WHY NOT USE... • Memcached? • MongoDB? • Postgres/MySQL?
  • Hierarchical data structure in znodes
  • • Session Based • Znode watches • Ephemeral and Sequential Znodes
  • • Last for duration of client session • Session dies when connection is closed or expires • Can’t have children znodes EPHEMERAL ZNODES
  • SEQUENTIAL ZNODES • Supply a node name (or not), get node name back with a trailing sequence number (0001, 0002, 0003, etc.) • Can be combined with ephemeral flag
  • BASIC COMMANDS • create(PATH, DATA...) • get(PATH...) • get_children(PATH...) • set(PATH, DATA...) • delete(PATH...)
  • PYTHON CLIENTS • txzookeeper • kazoo • unified client that works with gevent • implements wire protocol in pure Python
  • USE KAZOO
  • EASY TO USE from kazoo.client import KazooClient client = KazooClient() client.start()
  • USE CASES
  • CONFIGURATION • Store settings in node data • Organize node structure • Set watches on nodes of interest
  • PARTY MEMBERSHIP • Join a party, find out who else is around • Elect a leader if desired • Recipe in Kazoo
  • LOCKS • Lock a resource for a single client • Lock a resource for multiple clients (Semaphore) • Hard to write properly • Recipe in Kazoo
  • BUILDING HIGHER LEVEL ABSTRACTIONS ON ZOOKEEPER
  • CAVEAT
  • DO NOT IMPLEMENT YOURSELF USE THE RECIPE
  • BASIC STEPS • Create lock parent node if needed • Create ephemeral+sequence node under parent, store node name returned • Get children of lock node • Sort children list by sequence number • First child in the list has the lock!
  • THINGS TO WATCH OUT FOR • Avoid the thundering herd, use watches only when needed • When our node isn’t the lowest, watch the one in front of us • Only one client wanting a lock is ‘woken’ when the lock is released by a different client
  • HANDLING FAILURE
  • ROBUST CODE TAKES EFFORT • What happens when a server fails? • What happens when the client fails? • What happens when we don’t know if the server has failed?
  • STOPPING WHEN UNCERTAIN
  • A BIT BETTER VERSION...
  • EVEN BETTER
  • FAILURE WILL HAPPEN • Fail fast, fail completely. • Session expiration is a good time to sys.exit • Always include jitter (kazoo includes jitter on its connection and command retry operations) • Consider what exceptions can occur in any code relying on a distributed system
  • • Distributed systems are hard • Use existing battle-proven tools (Zookeeper, Kazoo) • Always consider everything that can fail, and how • Be wary of tools that don’t tell you how they fail • Read Kyle Kingsbury’s Jepsen posts to see examples of systems failing: http://aphyr.com/tags/jepsen
  • FIN
  • QUESTIONS?