Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zookeeper_url split into two vars, Easy to change the download address #1

Open
wants to merge 100 commits into
base: master
Choose a base branch
from

Conversation

cifaz
Copy link

@cifaz cifaz commented Apr 26, 2018

zookeeper_url split into two vars, Easy to change the download address

mhamrah and others added 30 commits October 24, 2014 21:46
Supporting RHEL 6 systems
Zookeeper service had state=restarted which cause that every time
when playbook were run, Zookeeper restart.
Added restart handler added notifications to all config files and
changed state to "started".
Removed unneeded Zookeeper restart on every run
Ansible were restarting Zookeeper every time Ansible were running.
Fixed service state=started and added restart handlers to restart
only if configuration changes.
Fixed Zookeeper to restart every time Ansible runs on Debian
It's time to update the version and given that the playbook has been around I believe a v0.9.0 is in order.
Builds will fail if using 3.4.6 for the version because Apache removes
old versions from their mirrors for some ungodly reason.
Bump default zookeeper_version to 3.4.7
Bump playbook version to 0.9.1
Apache has removed ZK 3.4.7 from their mirrors, causing builds to fail again.

I followed up in #zookeeper to see why these releases keep disappearing from the mirrors,
so hopefully we'll get some answers as to how to prevent this going forward.
BYPASS - Update version
…ervice_enabled_for_redhat

Make zookeeper service enabled for RedHat
ernestas-poskus and others added 30 commits May 10, 2017 10:30
The latest Zookeeper version 3.5.3-beta is distributed as plain tar
archive, so `tar zxf` fails with `gzip: stdin: not in gzip format`.

Also, recent versions of tar recognize format by itself, so there is no
need in 'z' option.
Currently, when running ansible-zookeeper role on Debian 8 host, it
fails:

    TASK [AnsibleShipyard.ansible-zookeeper : Enable zookeeper service] ***************************************************
    fatal: [debian8-host]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service zookeeper: host"}

This happens because `zookeeper_debian_systemd_enabled` variable is
enabled only for Ubuntu >= 15.04 hosts.

This PR adds check for Debian >= 8.0, so Zookeeper successfully installs
on Debian 8.0
Enable systemd service for Debian 8
…cker_version_constraint

Remove .travis specific docker version constraint
…ersion_to_3_4_11

Bump zookeper version to 3.4.11
In order to avoid name-resolution and connectivity issues to other cluster nodes, make sure ZK only starts up after the network has started up properly.
* Extracted hardcoded zookeeper ports into vars

* Set proper variable for test
replace the hard coded /var/log/zookeeper with {{log_dir}} variable
Update zookeeper.conf.j2
max_client_connections ->maxClientCnxns
Customize own hostname with a new variable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.