| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
also accept vhostpath.
|
| | |
|
| |\
| |
| | |
[OCF HA] On neighbor promotion do nothing if we are already clustered
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
+ extracted function checking if we are in the same cluster with
given node
+ made post-promote ignore promotion of self. Previously it was
done inside jjj_join, but now we need to do that before the
new check.
+ now we write "post-promote end" log entry at the very
end of post-promote, not somewhere in the middle.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Doing otherwise causes node to restart when get_monitor is called
within action_promote - it does not find a master and assumes that
it is running out of cluster.
Also, code is refactored a little bit - a new function returning
current master is created and is used in the changed code.
|
| |\ \
| |/
|/| |
Unescape list_permissions and list_user_permissions regexes
|
| |/ |
|
| |\
| |
| | |
[OCF HA] Increase tolerable number of rabbitmqctl timeouts
|
| |/
|
|
|
|
|
|
|
| |
We still see that rabbitmqctl list_channels times out from time
to time, though the RabbitMQ cluster is absolutely healthy in any
other aspect.
Setting max_rabbitmqctl_timeouts to 3 seems to be a sane default
to help avoid unnecessary restarts.
|
| |\
| |
| | |
Windows installer: don't jump to the finish page on install/uninstall
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Private attributes usage in rabbitmq script
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There are three types of rabbitmq attributes for pacemaker nodes:
-'rabbit-master'
-'rabbit-start-time'
- timeouts:
-'rabbit_list_channels_timeouts'
-'rabbit_get_alarms_timeouts'
-'rabbit_list_queues_timeouts'
Attributes with names 'rabbit-master' and 'rabbit-start-time' should be
public because we monitor this attributes in cycle for all nodes in our
script.
All timeouts attributes were changed to private to avoid unnecessary
transitions.
Also, --lifetime and --node options were removed for attrd_updater as
'lifetime' for this command is always 'reboot' and 'node' default value
is local one.
|
| |\ \
| | |
| | | |
Exit waiting loop once node has unjoined
|
| | | |
| | |
| | |
| | |
| | | |
Without the break we always wait for 50 seconds, even if we don't need
to wait at all.
|
| |\ \ \
| | | |
| | | | |
Introduce rabbit.channel_operation_timeout
|
| | |\ \ \
| | | |/
| | |/| |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Per discussion with Ayanda. Lower values
are known to produce false positives in a variety
of contexts.
|
| | | | |
| | | |
| | | |
| | | | |
To update to a higher value in future, for cross-node calls.
|
| | | | |
| | | |
| | | |
| | | | |
References: #248
|
| | | | |
| | | |
| | | |
| | | | |
Spaces were mixed with tabs, though make(1) expects the latter.
|
| | |/ /
|/| |
| | |
| | |
| | | |
Before, a failure from xmlto(1) was ignored and the build continued
"happily".
|
| |\ \ \
| |_|/
|/| | |
Added erl call to make sure epmd is started
|
| | | | |
|
| |/ / |
|
| | | |
|
| |\ \
| | |
| | | |
rabbit_mirror_queue_sync: Pause the syncer process if memory is low
|
| |/ /
| |
| |
| |
| |
| |
| | |
If any node in the cluster is running out of memory, we pause the syncer
process. If we don't do this, this alarmed node could crash.
Fixes #616.
|
| | |
| |
| |
| |
| | |
Alarms are emitted for 'disk' or 'memory' resources shortage, not
'node'.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
RabbitMQ recreates it anyway so we can't pass it the escaped directory
name. Therefore, this directory must not contain any non-US-ASCII in its
name.
References #493.
|
| |\ \
| | |
| | | |
Fix action_stop for the rabbit OCF
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The action_stop may sometimes stop the rabbitmq-server gracefully
by the PID, but leave unresponsive beam.smp processes running and
spoiling rabbits. Those shall be stopped as well. The solution is:
- make proc_stop() to accept a pid=none to use a name matching instead
- make kill_rmq_and_remove_pid() to stop by the beam process matching as well
- fix stop_server_process() to ensure there is no beam process left running
Related Fuel bug: https://launchpad.net/bugs/1541029
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
|
| |\ \
| | |
| | | |
Add emitting node info to amq.rabbitmq.log messages
|
| |/ /
| |
| |
| | |
Fixes #595.
|
| |\ \
| | |
| | | |
Streamline checking for cluster partitioning
|
| |/ /
| |
| |
| |
| | |
Move check if we are current cluster master to earlier place in code.
That way we will avoid unnecessary operations for master case.
|
| |\ \
| | |
| | | |
Fix cluster membership check for running master
|
| | |/
| |
| |
| | |
The running master is always inside of its own cluster.
Fix the cluster membership check when a node is the master.
|
| |\ \
| |/
| | |
Fix uninitialized status_master
|
| |/
|
|
|
|
|
|
| |
Fix multiple nodes may be reported in logs as the running master
Related Fuel bug https://bugs.launchpad.net/bugs/1540936
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
|
| |\
| |
| | |
Suppress curl progress indicator in rabbit OCF
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
curl is used by OCF script for fetching definitions (queues etc.), but
results of that invocation is shown as garbage in pacemaker logs -
progress indicator doesn't make any sense in logs.
According to curl manpage the following combination of options should be
used "--silent --show-error" - this will suppress only progress
indicator, errors will still be shown.
Also other short curl options are replaced with their long counterparts
- for improved readability.
|
| |\
| |
| | |
Use -r with sed on Linux
|
| |/
|
|
|
|
|
|
| |
We previously did the same change in #273 (PR: #275),
but the file in which it was done was removed in 231e90cacf3daec5f43b3307867129e61496b123.
Note that #592 recommends using `-r` unconditionally but that option
is not recognised by sed which ships with OS X.
|
| |\
| |
| |
| |
| |
| |
| |
| | |
This is only a part of what #541 is supposed to cover but
it already helped in a particular node shutdown lockup we've
observed => worth merging earlier.
Per discussion with @dcorbacho.
|
| | |\ |
|
| | | | |
|
| | | | |
|
