| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
For offset (e.g. offset=5000) and timestamp (timetamp=5000).
It was ":" before, but this is already the separator for key/value
in STOMP headers. This was actually working with the client used
to test, but other clients may get confused.
References #3002.
|
| |
|
|
|
|
|
|
|
|
| |
This commit introduces the support of an x-stream-offset header
in the SUBSCRIBE frame to start consuming from a specific place
in a stream. The possible values are first, last, next, offset:<offset-value>
(e.g. offset:40000), timestamp:<timestamp-in-seconds> (e.g. timestamp:1619428685).
This commit also propagates the x-stream-offset header in the MESSAGE frame
to know the offset of a the delivered message in the stream.
|
| |\
| |
| | |
Ignore drained nodes when rebalancing
|
| | |
| |
| |
| |
| |
| | |
It did not solve the problem and made the failure slower.
This reverts commit 510230302e0adf657b3f6f7c849962ae9796ca2a.
|
| | |
| |
| |
| |
| |
| | |
Classic queue mirrors should also continue pushing messages to disk when syncing
(cherry picked from commit a728662fd79e00b1c1713111d2fcfe5a9113753e)
|
| | |
| |
| |
| |
| | |
So that faulty consumers that will never ack a pending messages have
their channels closed after 15 minutes.
|
| | |
| |
| |
| |
| |
| | |
This is executed once per queue so potentially many, many, times
and a dirty read is much faster. The state of maintenance mode
on the nodes is unlikely to change during rebalancing.
|
| | |
| |
| |
| |
| | |
Transfer leadership is a slow command, it's acceptable to wait until
the ra cluster is ready to answer
|
| | |
| |
| |
| | |
When running `rabbitmq-queues rebalance`, drained nodes (nodes in maintenance mode) should not recive QQ leaders nor CMQ masters.
|
| |\ \
| | |
| | | |
Tag docker image with branch name
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
in addition to tagging the docker image with the Git commit SHA.
This enables the cluster-operator to run system-tests against latest
rabbitmq-server master branch which allows us to fix any breaking
changes early and to test unreleased features such as rabbitmq_stream
plugin.
|
| | |
| |
| |
| |
| |
| | |
Classic queue mirrors should also continue pushing messages to disk when syncing
(cherry picked from commit a728662fd79e00b1c1713111d2fcfe5a9113753e)
|
| |\ \
| |/
|/| |
Set a default for consumer_timeout
|
| | |
| |
| |
| |
| | |
So that faulty consumers that will never ack a pending messages have
their channels closed after 15 minutes.
|
| |\ \
| | |
| | | |
Allow AMQP error responses in channel interceptors
|
| |/ / |
|
| |\ \
| |/
|/| |
Mk decode other name as directory string
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
and assume it is a string-like value ("directory string")
because other values would not make much sense in the
username extraction context.
References #2983.
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
instead of specific ones since they will vary with the payload
(one of them likely indicates UTF string length).
This is still not perfect because we limit the maximum
allowed length but it works fine with identifiers up to 100
characters long, which should be good enough for this
best effort handling of an abscure SAN type.
References ##2983.
|
| | |
|
| | |
|
| |
|
|
| |
We no longer support it even in v3.8.x.
|
| |
|
|
|
| |
x.509 certificate extensions do not really have types in
OTP's public_key, so our hands are tied.
|
| | |
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
The parser didn't handle literals of the form:
'single-quoted'unquoted'single-quoted-again'"or-even-double-quoted"
In particular, the unquoted parsing assumed that nothing else could
follow it. The testsuite is extended with the issue reporter's case.
While here, improve escaped characters handling. They used to be not
parsed specifically at all.
Fixes #2969.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
x.509 certificate auth mechanism: support (some) SANS of type otherName
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note that the type by definition contains arbitrary values. According
to the OTP types, they are triplets that represent effectively
a key/value pair. So we assume the pair is a string that needs a bit
massaging, namely stripping the UTF encoding prefix OTP AnotherName
decoder leaves in.
Kudos to @Thibi2000 for providing an example value.
Closes #2983.
|
| |/ |
|
| | |
|
| |
|
| |
No longer valid, use the usual process to run a plugin.
|
| |\
| |
| | |
Correctly parse tags provided as a list
|
| | | |
|
| | |
| |
| |
| | |
Discovered while testing a PR for rabbit-hole
|
| |\ \
| |/
|/| |
Set correct field for extra scope and improve doc
|
| |/
|
|
|
| |
- Replace additional_rabbitmq_scopes in doc for the correct extra_scopes_source value
- Add samples
- More details for audiance checkup on token
|
| |
|
|
| |
That regressed after refactoring how delivery effects are emitted.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This should alleviate lack of disk space in github actons
|
| |\
| |
| | |
QQ: ensure that messages are delivered in order
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the case where there are some messages kept in memory mixed with
some that are not it is possible that a messages are delivered to the
consuming channel with gaps/out of order which would in some cases cause
the channel to treat them as re-sends it has already seen and just
discard them. When this happens the messages get stuck in the consumer
state inside the queue and are never seen by the client consumer and
thus never acked. When this happen the release cursors can't be emitted
as the smallest raft index will be one of the stuck messages.
|
| | | |
|
| | | |
|
| | | |
|
