This repository has been archived by the owner on Sep 18, 2021. It is now read-only.
forked from liquidgecka/twitcher
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Initial commit of Twitcher for the public repository.
Twitcher is a process for running scripts when znodes change in ZooKeeper. It was initially written by Brady Catherman for use inside of Twitter and is being open sourced with Twitter's permission under the Apache 2.0 license. For more information please read the README in the top level directory.
- Loading branch information
Brady Catherman
committed
Jul 17, 2010
0 parents
commit 824753a
Showing
13 changed files
with
1,895 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,202 @@ | ||
|
||
Apache License | ||
Version 2.0, January 2004 | ||
http://www.apache.org/licenses/ | ||
|
||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION | ||
|
||
1. Definitions. | ||
|
||
"License" shall mean the terms and conditions for use, reproduction, | ||
and distribution as defined by Sections 1 through 9 of this document. | ||
|
||
"Licensor" shall mean the copyright owner or entity authorized by | ||
the copyright owner that is granting the License. | ||
|
||
"Legal Entity" shall mean the union of the acting entity and all | ||
other entities that control, are controlled by, or are under common | ||
control with that entity. For the purposes of this definition, | ||
"control" means (i) the power, direct or indirect, to cause the | ||
direction or management of such entity, whether by contract or | ||
otherwise, or (ii) ownership of fifty percent (50%) or more of the | ||
outstanding shares, or (iii) beneficial ownership of such entity. | ||
|
||
"You" (or "Your") shall mean an individual or Legal Entity | ||
exercising permissions granted by this License. | ||
|
||
"Source" form shall mean the preferred form for making modifications, | ||
including but not limited to software source code, documentation | ||
source, and configuration files. | ||
|
||
"Object" form shall mean any form resulting from mechanical | ||
transformation or translation of a Source form, including but | ||
not limited to compiled object code, generated documentation, | ||
and conversions to other media types. | ||
|
||
"Work" shall mean the work of authorship, whether in Source or | ||
Object form, made available under the License, as indicated by a | ||
copyright notice that is included in or attached to the work | ||
(an example is provided in the Appendix below). | ||
|
||
"Derivative Works" shall mean any work, whether in Source or Object | ||
form, that is based on (or derived from) the Work and for which the | ||
editorial revisions, annotations, elaborations, or other modifications | ||
represent, as a whole, an original work of authorship. For the purposes | ||
of this License, Derivative Works shall not include works that remain | ||
separable from, or merely link (or bind by name) to the interfaces of, | ||
the Work and Derivative Works thereof. | ||
|
||
"Contribution" shall mean any work of authorship, including | ||
the original version of the Work and any modifications or additions | ||
to that Work or Derivative Works thereof, that is intentionally | ||
submitted to Licensor for inclusion in the Work by the copyright owner | ||
or by an individual or Legal Entity authorized to submit on behalf of | ||
the copyright owner. For the purposes of this definition, "submitted" | ||
means any form of electronic, verbal, or written communication sent | ||
to the Licensor or its representatives, including but not limited to | ||
communication on electronic mailing lists, source code control systems, | ||
and issue tracking systems that are managed by, or on behalf of, the | ||
Licensor for the purpose of discussing and improving the Work, but | ||
excluding communication that is conspicuously marked or otherwise | ||
designated in writing by the copyright owner as "Not a Contribution." | ||
|
||
"Contributor" shall mean Licensor and any individual or Legal Entity | ||
on behalf of whom a Contribution has been received by Licensor and | ||
subsequently incorporated within the Work. | ||
|
||
2. Grant of Copyright License. Subject to the terms and conditions of | ||
this License, each Contributor hereby grants to You a perpetual, | ||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable | ||
copyright license to reproduce, prepare Derivative Works of, | ||
publicly display, publicly perform, sublicense, and distribute the | ||
Work and such Derivative Works in Source or Object form. | ||
|
||
3. Grant of Patent License. Subject to the terms and conditions of | ||
this License, each Contributor hereby grants to You a perpetual, | ||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable | ||
(except as stated in this section) patent license to make, have made, | ||
use, offer to sell, sell, import, and otherwise transfer the Work, | ||
where such license applies only to those patent claims licensable | ||
by such Contributor that are necessarily infringed by their | ||
Contribution(s) alone or by combination of their Contribution(s) | ||
with the Work to which such Contribution(s) was submitted. If You | ||
institute patent litigation against any entity (including a | ||
cross-claim or counterclaim in a lawsuit) alleging that the Work | ||
or a Contribution incorporated within the Work constitutes direct | ||
or contributory patent infringement, then any patent licenses | ||
granted to You under this License for that Work shall terminate | ||
as of the date such litigation is filed. | ||
|
||
4. Redistribution. You may reproduce and distribute copies of the | ||
Work or Derivative Works thereof in any medium, with or without | ||
modifications, and in Source or Object form, provided that You | ||
meet the following conditions: | ||
|
||
(a) You must give any other recipients of the Work or | ||
Derivative Works a copy of this License; and | ||
|
||
(b) You must cause any modified files to carry prominent notices | ||
stating that You changed the files; and | ||
|
||
(c) You must retain, in the Source form of any Derivative Works | ||
that You distribute, all copyright, patent, trademark, and | ||
attribution notices from the Source form of the Work, | ||
excluding those notices that do not pertain to any part of | ||
the Derivative Works; and | ||
|
||
(d) If the Work includes a "NOTICE" text file as part of its | ||
distribution, then any Derivative Works that You distribute must | ||
include a readable copy of the attribution notices contained | ||
within such NOTICE file, excluding those notices that do not | ||
pertain to any part of the Derivative Works, in at least one | ||
of the following places: within a NOTICE text file distributed | ||
as part of the Derivative Works; within the Source form or | ||
documentation, if provided along with the Derivative Works; or, | ||
within a display generated by the Derivative Works, if and | ||
wherever such third-party notices normally appear. The contents | ||
of the NOTICE file are for informational purposes only and | ||
do not modify the License. You may add Your own attribution | ||
notices within Derivative Works that You distribute, alongside | ||
or as an addendum to the NOTICE text from the Work, provided | ||
that such additional attribution notices cannot be construed | ||
as modifying the License. | ||
|
||
You may add Your own copyright statement to Your modifications and | ||
may provide additional or different license terms and conditions | ||
for use, reproduction, or distribution of Your modifications, or | ||
for any such Derivative Works as a whole, provided Your use, | ||
reproduction, and distribution of the Work otherwise complies with | ||
the conditions stated in this License. | ||
|
||
5. Submission of Contributions. Unless You explicitly state otherwise, | ||
any Contribution intentionally submitted for inclusion in the Work | ||
by You to the Licensor shall be under the terms and conditions of | ||
this License, without any additional terms or conditions. | ||
Notwithstanding the above, nothing herein shall supersede or modify | ||
the terms of any separate license agreement you may have executed | ||
with Licensor regarding such Contributions. | ||
|
||
6. Trademarks. This License does not grant permission to use the trade | ||
names, trademarks, service marks, or product names of the Licensor, | ||
except as required for reasonable and customary use in describing the | ||
origin of the Work and reproducing the content of the NOTICE file. | ||
|
||
7. Disclaimer of Warranty. Unless required by applicable law or | ||
agreed to in writing, Licensor provides the Work (and each | ||
Contributor provides its Contributions) on an "AS IS" BASIS, | ||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or | ||
implied, including, without limitation, any warranties or conditions | ||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A | ||
PARTICULAR PURPOSE. You are solely responsible for determining the | ||
appropriateness of using or redistributing the Work and assume any | ||
risks associated with Your exercise of permissions under this License. | ||
|
||
8. Limitation of Liability. In no event and under no legal theory, | ||
whether in tort (including negligence), contract, or otherwise, | ||
unless required by applicable law (such as deliberate and grossly | ||
negligent acts) or agreed to in writing, shall any Contributor be | ||
liable to You for damages, including any direct, indirect, special, | ||
incidental, or consequential damages of any character arising as a | ||
result of this License or out of the use or inability to use the | ||
Work (including but not limited to damages for loss of goodwill, | ||
work stoppage, computer failure or malfunction, or any and all | ||
other commercial damages or losses), even if such Contributor | ||
has been advised of the possibility of such damages. | ||
|
||
9. Accepting Warranty or Additional Liability. While redistributing | ||
the Work or Derivative Works thereof, You may choose to offer, | ||
and charge a fee for, acceptance of support, warranty, indemnity, | ||
or other liability obligations and/or rights consistent with this | ||
License. However, in accepting such obligations, You may act only | ||
on Your own behalf and on Your sole responsibility, not on behalf | ||
of any other Contributor, and only if You agree to indemnify, | ||
defend, and hold each Contributor harmless for any liability | ||
incurred by, or claims asserted against, such Contributor by reason | ||
of your accepting any such warranty or additional liability. | ||
|
||
END OF TERMS AND CONDITIONS | ||
|
||
APPENDIX: How to apply the Apache License to your work. | ||
|
||
To apply the Apache License to your work, attach the following | ||
boilerplate notice, with the fields enclosed by brackets "[]" | ||
replaced with your own identifying information. (Don't include | ||
the brackets!) The text should be enclosed in the appropriate | ||
comment syntax for the file format. We also recommend that a | ||
file or class name and description of purpose be included on the | ||
same "printed page" as the copyright notice for easier | ||
identification within third-party archives. | ||
|
||
Copyright [yyyy] [name of copyright owner] | ||
|
||
Licensed 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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,186 @@ | ||
================ | ||
=== Twitcher === | ||
================ | ||
|
||
1. License | ||
2. Overview | ||
3. Installation | ||
4. Configuration Language | ||
4.1 Examples | ||
4.2 Things to Avoid | ||
5. Known Issues | ||
6. Future Features | ||
7. Change Log | ||
|
||
1. License | ||
========== | ||
|
||
This software is licensed under the Apache 2.0 license. Please see LICENSE | ||
in the top level of this git repository for more information. | ||
|
||
2. Overview | ||
=========== | ||
|
||
Twitcher is a minimal tool used to run scripts when a znode in ZooKeeper | ||
changes. The intent is to allow various system tasks to take place on a | ||
watched model rather than via polling. | ||
|
||
The best description of Twitcher is to highlight an example that it solves | ||
very well. Lets assume we are facing a problem where we need a single git | ||
repository to be checked out and up to date on 100 machines in a cluster. The | ||
typical solution to this is to add a cron job that performs a git pull every | ||
minute. This can be problematic as your git server has to endure the load of | ||
100 servers performing a pull every minute. You can configure Twitcher on all | ||
machines to watch /git/head on your ZooKeeper instance. When that znode | ||
changes Twitcher can run git pull. Add a post-commit script in your main | ||
git repository that pokes that file and you will be able to fetch updates | ||
within few seconds of a commit on all machines while not requiring constant | ||
fetching when no changes are being made. | ||
|
||
3. Installation | ||
=============== | ||
|
||
The default installation of Twitcher places the twitcher binary (bin/twitcher) | ||
in /usr/sbin and the twitcher module (twicher/*) in the site-packages | ||
directory which is often /usr/lib/python2.6/sites-packages/twitcher. | ||
|
||
The configs are read recursively from /etc/twitcher while twitcher is running. | ||
|
||
Note that Twitcher uses inofity to update when files change so it can | ||
automatically reload them. This is used to allow quick adding and removing | ||
of configs without restarting the server binary. If a config fails to parse | ||
then it will not be updated in the running binary and a log message will be | ||
written. | ||
|
||
By default Twitcher uses syslog under daemon as the default logging method. | ||
|
||
4. Configuration Language | ||
========================= | ||
|
||
The configuration language for Twitcher is actually just python. Each | ||
configuration must register a znode, and an action for each watch it wants. | ||
This is done via a RegisterWatch function which takes several arguments. | ||
|
||
RegisterWatch(): Creates a watch that will run a script when a Zookeeper node | ||
is updated. | ||
znode: This is the znode in ZooKeeper that is to be watched. | ||
action: This is a function or lambda that will perform an action when | ||
the znode is modified. The most common use here is to call Exec() | ||
which is a function documented later. | ||
pipe_stdin: If True then the contents of 'znode' will be piped to the stdin | ||
of the processes running action. Default is True. | ||
run_on_load: If True then the action will be executed when Twitcher starts. | ||
Without this your action may miss updates. | ||
The default is True. | ||
run_mode: This defines how Twitcher will react when 'znode' is updated | ||
while it is running 'action' for a previous update. The optional | ||
modes are: | ||
QUEUE: This will queue the watch until the currently running | ||
'action' finishes, then run 'action' with the most | ||
recent contents. If several watches are received while | ||
'action' is running then only the last update will | ||
be executed. | ||
DISCARD: Ignore the update, don't run the script, but | ||
re-register the watch. | ||
PARALLEL: Run the script in parallel for every update received. | ||
The default run mode is QUEUE. | ||
uid: The user id to run the process as (string or int). The default is to | ||
run as root. | ||
gid: The group id to run the process as (string or int). The default is to | ||
run as root. | ||
description: This is a text description of the watch which will be used | ||
for logging. The default is to name watches after the file | ||
they are configured in. | ||
|
||
Exec(): Returns a lambda that will execute a given command when run. | ||
command: If this is a string then the command will be invoked in a | ||
shell interpreter. If its a list then it will be executed | ||
exactly as specified. | ||
|
||
By default the configuration files should be placed in /etc/twitcher and | ||
should use an extension of ".twc". | ||
|
||
|
||
4.1. Examples | ||
============= | ||
|
||
In this example config a node called '/twitcher/example1' will be watched for | ||
updates, and when it changes it will execute | ||
"date >> /tmp/twitcher_example1.out". | ||
|
||
RegisterWatch( | ||
znode='/twitcher/example1', | ||
action=Exec('date >> /tmp/twitcher_example1.out') | ||
) | ||
|
||
As another example we can run a python function rather than executing a | ||
command. For this example we will execute the function example2() every time | ||
'/twitcher/example2' is updated. | ||
|
||
def example2(): | ||
open('/tmp/twitcher_example2.out', 'w').write('testing') | ||
|
||
RegisterWatch( | ||
znode='/twitcher/example2', | ||
action=example2 | ||
) | ||
|
||
Keep in mind that the action function is run in a process that has been forked | ||
off from the main Twitcher instance. As such the following example | ||
DOES NOT WORK AS EXPECTED. The output will always be 1 since the increment | ||
happens in the child process which exits after doesnotwork() finishes. | ||
|
||
x = 0 | ||
def doesnotwork(): | ||
global x | ||
x += 1 | ||
open('/tmp/twitcher_badexample.out', 'w').write(x) | ||
|
||
RegisterWatch( | ||
znode='/twitcher/doesnotwork', | ||
action=doesnotwork | ||
) | ||
|
||
4.2 Things to Avoid | ||
=================== | ||
|
||
Any action run by Twitcher is expected to by idempotent. Since the script may | ||
be executed at any time and can be triggered rapidly it is expected that | ||
each script does basic health and sanity checking before performing expensive | ||
or destructive actions. | ||
|
||
Even if the script is in QUEUE mode there is a possibility that it may be run | ||
twice. If Twitcher is restarted while the script is running it will then | ||
restart the script when Twitcher restarts which leaves two running at the | ||
same time. In order to prevent this your script should use file based sigil | ||
or other method to verify exclusivity. | ||
|
||
5. Known Issues | ||
=============== | ||
|
||
None at the moment. | ||
|
||
6. Future Features | ||
================== | ||
|
||
Timeouts on the child processes: Allow the config to set a timeout after which | ||
the script will be considered failed. | ||
|
||
Failure handling on the child process: Allow the config to specify what should | ||
be done in the case where the script fails (returns non zero). Some examples | ||
include "retry x times" "fail but keep watch" "fail and stop watching" | ||
|
||
7. Change Log | ||
============= | ||
|
||
Release: 1.2, Open source under the Apache 2.0 license. | ||
|
||
2010/7/15: Added uid/gid support | ||
|
||
Release: 1.1 | ||
|
||
2010/6/24: Fixed a bug that allowed child processes to get ignored forever. | ||
|
||
Release 1.0 | ||
|
||
2010/6/19: Initial review. |
Oops, something went wrong.