summaryrefslogtreecommitdiffstats
path: root/system/zookeeper/README
diff options
context:
space:
mode:
author Andre Barboza <bmg.andre@gmail.com>2016-01-12 06:53:41 +0700
committer Robby Workman <rworkman@slackbuilds.org>2016-01-12 21:58:11 -0600
commitaa59088973d5d87c7ed9875b91bb6a202735e1bd (patch)
treef1e890587772b3871107620de37c4b53a989ce02 /system/zookeeper/README
parent5bfc33d67c95c024cddbc2da901a13e5ffaebd5c (diff)
downloadslackbuilds-aa59088973d5d87c7ed9875b91bb6a202735e1bd.tar.gz
slackbuilds-aa59088973d5d87c7ed9875b91bb6a202735e1bd.tar.xz
system/zookeeper: Added (distributed coordination server).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/zookeeper/README')
-rw-r--r--system/zookeeper/README16
1 files changed, 16 insertions, 0 deletions
diff --git a/system/zookeeper/README b/system/zookeeper/README
new file mode 100644
index 0000000000..a752f3834e
--- /dev/null
+++ b/system/zookeeper/README
@@ -0,0 +1,16 @@
+ZooKeeper is a centralized service for maintaining configuration information,
+naming, providing distributed synchronization, and providing group services.
+All of these kinds of services are used in some form or another by distributed
+applications. Each time they are implemented there is a lot of work that goes
+into fixing the bugs and race conditions that are inevitable. Because of the
+difficulty of implementing these kinds of services, applications initially
+usually skimp on them ,which make them brittle in the presence of change and
+difficult to manage. Even when done correctly, different implementations of
+these services lead to management complexity when the applications are
+deployed.
+
+This script requires a 'zookeeper' user/group to exist before running.
+The recommended UID/GID is 322. You can create these like so:
+
+groupadd -g 322 zookeeper
+useradd -u 322 -g 322 -c "Zookeeper user" -d /var/lib/zookeeper -s /bin/sh zookeeper