Database takes 40 mins to start, replication process needs to manually start after

Archives Ansible Project
1

Hi,
Today I setup a playbook to upgrade our CitrusLeaf NoSQL database
server. The database takes between 25 and 50 minutes to start based
on the particular cluster and hardware. When I start the server
manually the way I know the server is ready is to tail the log for the
word cake i.e. tail -f /var/log/citrusleaf.log | grep -i cake. There
are other commands I can run to see if the server has started, but are
generally run for other information.

Is there away I can get ansible to recognize that the process has
completed starting up? I would like to have the playbook complete
other tasks after the database has started, and upgrade the next host
in the cluster.

Thanks,
James

2

Looked at wait_for?

http://ansible.cc/docs/modules.html#wait-for

polls until a port is open

3

Thanks! totally forgot about this module and when it was announced I
thought I'll use that.

Thanks,
James