| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |\
| | |
| | | |
Deb repository: Use SIGNING_KEY to select the repository signing key
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the only way to select a specific subkey. The user ID is useless
for that.
References #718.
[#118296861]
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
By default, honor the default key; usually it is specified in
`gpg.conf`.
References #718.
[#118296861]
|
| |\ \
| |/ |
|
| | |\ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #570
With this patch systemd service file will be used on systemd-enabled
hosts, providing more seamless experience.
I've tested it by building it on ubuntu 14.04, which is not managed by
systemd. Still, it has necessary packages to build systemd-aware
debs. And then I tried to install this package:
- On ubuntu 14.04 - regular init script was used
- On debian jessie with systemd and esl-erlang 18.3 - server was
properly started using systemd service file (and epmd dependency was
also automatically started by systemd)
|
| |\ \
| |/ |
|
| | |\
| | |
| | | |
Use AckRequired in drop_one as priority queues return tuples {Priority, AckTag}
|
| | | |\ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Fetch and drop operations of priority queues' consumers with no_ack=true,
were changed internally to no_ack=false in the requests to the mirror slaves.
Those messages would never be acknowledge by the consumer, as it was not part
of the consumers configuration.
|
| |\ \ \ \
| |/ / / |
|
| | |\ \ \
| | |_|/
| |/| | |
Use max priority for higher priorities when returning backing queue state
|
| | | |\ \
| | |/ /
| |/| | |
|
| | | |\ \ |
|
| | | | |/
| | |/|
| | | |
| | | | |
* Needed in synchronisation, otherwise messages for higher priorities are dropped in the slave
|
| |\ \ \ \
| | | | |
| | | | | |
Listing items in parallel
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Current implementation of various `list_XXX` commands require cross-node
roundtrip for every processed item - because `rabbitmqctl` target node
is responsible for gathering global list of all items of
interest (channels etc.) and then processing them one by one.
For example, listing 10000 channels evenly distributed across 3 nodes
where network has 1ms delay takes more than 10 seconds on my
machine. And with the proposed change listing will take almost the same
time as it'll take to gather this info locally. E.g. in the case above
listing now takes 0.7 second on the same machine with same 1ms delay.
It works by invoking emitting_map on every node, where it should send
info about only local items to aggregator, in an async fashion - as no
reply from aggregator is needed.
|
| |\ \ \ \ \
| | |/ / /
| |/| | | |
|
| | |\ \ \ \
| | |_|_|/
| |/| | | |
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
That way HiPE compilation can be performed during package installation
and will not waste time during every startup.
rabbit_hipe is refactored to support both modes of compilation - during
every server startup or separately with caching in the filesystem.
|
| | | | | |
|
| |\ \ \ \
| |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Neither rabbitmq nor any dependent services in chain actually relies on
syslog, so why keep it?
This tested in Fedora since 2016-01. See this commit:
http://pkgs.fedoraproject.org/cgit/rpms/rabbitmq-server.git/commit/?id=1477671
Nobody complained so far.
Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
|
| |\ \ \ \
| | | | |
| | | | | |
Remove systemd dependency on syslog target
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Neither rabbitmq nor any dependent services in chain actually relies on
syslog, so why keep it?
This tested in Fedora since 2016-01. See this commit:
http://pkgs.fedoraproject.org/cgit/rpms/rabbitmq-server.git/commit/?id=1477671
Nobody complained so far.
Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
|
| |\ \ \ \ \
| |/ / / /
|/| / / /
| |/ / / |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Bump minimal required version to 18.3
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | |/ / /
| |/| | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / / |
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
binarin/rabbitmq-server-systemd-example-wants-and-after
Add explicit epmd dependency in systemd example unit
|
| | |/ / / / |
|
| |\ \ \ \ \
| |/ / / / |
|
| | |\ \ \ \ |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / / |
|
| | |\ \ \ \ \
| | | |_|_|/
| | |/| | | |
Limit priority to maximum during synchronisation
|
| | | |/ / / |
|
| |\ \ \ \ \
| |/ / / / |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Private attributes usage in rabbitmq script
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Required Pacemaker >= 1.1.13.
(The command 'attrd_updater' have '-p' option only since this version).
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.
|
| |\ \ \ \ \
| |/ / / / |
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
| | | | /
| |_|_|/
|/| | | |
|
| | |/ / |
|
