该项目从 https://github.com/rabbitmq/rabbitmq-server 镜像。 拉取镜像更新于
  1. 16 8月, 2022 1 次提交
  2. 15 8月, 2022 1 次提交
  3. 12 8月, 2022 6 次提交
  4. 11 8月, 2022 8 次提交
    • Karl Nilsson's avatar
      rabbit_stream_queue flake improvement · 8b029d4a
      Karl Nilsson 创作于
      By waiting for the first remove_replica command to complete we
      may reduce the likelyhood of this test flaking.
      8b029d4a
    • Rin Kuryloski's avatar
      Merge pull request #5492 from rabbitmq/amqp10-client-system-flake · 28a802c5
      Rin Kuryloski 创作于
      amqp10_client system test suite reliability
      28a802c5
    • Karl Nilsson's avatar
      amqp10_client system test suite reliability · 784d3354
      Karl Nilsson 创作于
      Occasionally some system tests may fail as they start publishing
      before the credit event has been received. Added a wait for condition
      to avoid this.
      784d3354
    • Michael Klishin's avatar
      Merge pull request #5488 from rabbitmq/ik-update-prometheus-4.9-4380 · 1b28f597
      Michael Klishin 创作于
      Update prometheus to 4.9. close #4380
      1b28f597
    • Karl Nilsson's avatar
      Remove dependency on rabbit_channel in classic queues · ff1c3706
      Karl Nilsson 创作于
      Some queue -> channel messages were missed from classic queues
      when the queue type API was introduced. This commit fixes that
      which should make use of classic queues portable outside of the
      channel.
      
      This includes some refactoring to make more explicit that
      the stream_queue feature flag also enables queue types.
      ff1c3706
    • Iliia Khaprov's avatar
      update prometheus to 4.9. close #4380 · 5bbb088b
      Iliia Khaprov 创作于
      5bbb088b
    • Jean-Sébastien Pédron's avatar
      Merge pull request #5483 from rabbitmq/revert-prevent-overlapping-partitions · 3e96066b
      Jean-Sébastien Pédron 创作于
      Revert "Set kernel param prevent_overlapping_partitions to true"
      3e96066b
    • David Ansari's avatar
      Revert "Set kernel param prevent_overlapping_partitions to true" · fba455c6
      David Ansari 创作于
      This reverts commit 8070344a.
      
      We learnt during the last 6 days on master branch that RabbitMQ
      - as of today - is not compatible with kernel parameter
      `prevent_overlapping_partitions` set to `true`.
      
      RabbitMQ explicitly disconnects node in at least two places:
      1. rabbit_node_monitor to "promote" a partial network partition
      to a full partition, and
      2. rabbit_mnesia after a node reset to disconnect it from the
      rest of the cluster.
      There is no atomicity in the way we disconnect several nodes,
      because it's a simple loop. Therefore, remote nodes may/will detect
      disconnection at different times obviously. In global's new
      behavior behind prevent_overlapping_partitions, our attempt to
      disconnect all nodes in rabbit_mnesia creates a partial network
      partition from global's point of view, leading to a complete
      disconnection of the cluster.
      
      For example, test
      ```
      make ct-clustering_management t=cluster_size_3:join_and_part_cluster
      ```
      was flaky and demonstrates the 2nd bullet point above where RabbitMQ
      interfering with Erlang distribution conflicts with global's
      prevent_overlapping_partitions.
      When RabbitMQ resets a node, its last step is to loop over
      clustered nodes and disconnect from them one at a time.
      In this test with a 3-node cluster where we reset node A:
      1. Node A instructs node B and C to remove node A from their view
         of the cluster
      2. Node A disconnects from node B
      3. global on node B get a nodedow event for node A, but node C is
         still connected to node A
      4. global on node B concludes there is a network partition and
         disconnect from node A and node C
      At this point, each node is on its own.
      Nothing in RabbitMQ tries to restore the connection between
      nodes B and C.
      
      The correct path forward is:
      1. Get rid of Mnesia replacing it with Khepri.
      2. Once mirrored classic queues are removed, get rid of rabbit_node_monitor.
      3. Have a clear and consistent view of the nodes comprising a RabbitMQ Cluster:
         In other words, do not use different sources of truths like nodes(),
         Mnesia, Ra clusters, global monitor at different places in the code.
      
      For the time being we live with `prevent_overlapping_partitions` set to `false`
      and with the workaround for global:sync/0 being stuck introduced in
      https://github.com/rabbitmq/rabbitmq-server/commit/9fcb31f348590a74fd526333cf881cfbe27241e6
      fba455c6
  5. 10 8月, 2022 4 次提交
  6. 09 8月, 2022 5 次提交
  7. 08 8月, 2022 3 次提交
  8. 06 8月, 2022 6 次提交
  9. 05 8月, 2022 6 次提交