beetle 3.5.1 → 3.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2dcaf90eaf1b11b7f6350bb34e17d73591616790ede7b43b6e98cef363dd3770
-  data.tar.gz: 55348c9ce61cc2f43869f9c12cd26bbc5dc033b0e0a0506c0a821d6a6e24862c
+  metadata.gz: bce54bf1dc2290bb4c1598f6210b1c292d09691e91df2f67e913747535c90f2d
+  data.tar.gz: e6f510fb5b78a7ed0483f713920222ff1959e7a3e3073aac61abed25af56b0bd
 SHA512:
-  metadata.gz: 6daabfea72ab76b0fa6944d35cee52139678f9a02a272e86a32af6045750496ee81b96ff685eee1bbe9617030b981df3718b7569efabc98df59f894127da29d1
-  data.tar.gz: 04d599595b4c39e62a78b496b284a67bed1a545e759d9a094facc757e0334ed16e4bdd7bab4f7bfabb7b6f63da0e590351e86d0da55328ab6db898e9ceaaef7f
+  metadata.gz: 8682a1720108f7e95ad9802bcfe5b30283c735cfaa67323e5aca6bca1e1c06d0b6bb58d8fd2b8f4fc1fb7032579832667b78bab0c0f7013a937556650ad14ad7
+  data.tar.gz: 255b3fd3827a1f33c1c244967649ab8eaa1adc8f6daa3a111b21e299f1bcc0341f324a1bee3f2c578f5c93b39eeb913caf2c3a6d8ea88d1e89c028c48576e1b0

data/Rakefile

@@ -115,18 +115,14 @@ Rake::TestTask.new do |t|
   t.warning = false
 end
 
-require 'rdoc/task'
-
-RDoc::Task.new do |rdoc|
-  rdoc.rdoc_dir = 'site/rdoc'
-  rdoc.title    = 'Beetle'
-  rdoc.main     = 'README.rdoc'
-  rdoc.options << '--line-numbers' << '--inline-source' << '--quiet'
-  rdoc.rdoc_files.include('**/*.rdoc')
-  rdoc.rdoc_files.include('MIT-LICENSE')
-  rdoc.rdoc_files.include('lib/**/*.rb')
+task :clean do
+  sh "rm -f tmp/*.output tmp/*.log tmp/master-dir/* tmp/slave-dir/* tmp/*lock tmp/*pid test.log" unless ENV['GITHUB_ACTIONS']
 end
 
-task :clean do
-  sh "rm -f tmp/*.output tmp/*.log tmp/master-dir/* tmp/slave-dir/* tmp/*lock tmp/*pid test.log"
+require 'yard'
+
+YARD::Rake::YardocTask.new do |t|
+  OTHER_PATHS = %w()
+  t.files = ['lib/**/*.rb'] + OTHER_PATHS
+  t.options = %w(--markup-provider=redcarpet --markup=markdown --main=README.md --output-dir=site/yard)
 end

data/beetle.gemspec

@@ -39,8 +39,10 @@ Gem::Specification.new do |s|
   s.add_development_dependency "mocha",               "~> 1.3.0"
   s.add_development_dependency "mysql2",              "~> 0.4.4"
   s.add_development_dependency "rake",                "~> 13.0"
-  s.add_development_dependency "rdoc",                "~> 4.0"
   s.add_development_dependency "simplecov",           "~> 0.15"
   s.add_development_dependency "webmock",             "~> 3.0"
   s.add_development_dependency "websocket-eventmachine-client"
+  s.add_development_dependency 'yard'
+  s.add_development_dependency 'redcarpet'
+  s.add_development_dependency 'github-markup'
 end

data/examples/redundant.rb

@@ -17,7 +17,7 @@ Beetle.config.logger.level = Logger::INFO
 client = Beetle::Client.new
 
 # use two servers
-Beetle.config.servers = "localhost:5672, localhost:5673"
+Beetle.config.servers = ENV["RABBITMQ_SERVERS"] || "localhost:5672, localhost:5673"
 # instantiate a client
 client = Beetle::Client.new
 

data/examples/rpc.rb

@@ -4,7 +4,7 @@ require File.expand_path(File.dirname(__FILE__)+"/../lib/beetle")
 
 # suppress debug messages
 Beetle.config.logger.level = Logger::INFO
-Beetle.config.servers = "localhost:5672, localhost:5673"
+Beetle.config.servers = ENV["RABBITMQ_SERVERS"] || "localhost:5672, localhost:5673"
 # instantiate a client
 
 client = Beetle::Client.new

data/features/redis_auto_failover.feature

@@ -24,6 +24,26 @@ Feature: Redis auto failover
     Given a redis server "redis-1" exists as master
     Then the role of redis server "redis-1" should be "slave"
 
+  Scenario: Successful redis master switch with multiple slaves
+    And a redis server "redis-3" exists as slave of "redis-3"
+    Given a redis configuration server using redis servers "redis-1,redis-2,redis-3" with clients "rc-client-1,rc-client-2" exists
+    And a redis configuration client "rc-client-1" using redis servers "redis-1,redis-2,redis-3" exists
+    And a redis configuration client "rc-client-2" using redis servers "redis-1,redis-2,redis-3" exists
+    And a beetle handler using the redis-master file from "rc-client-1" exists
+    And redis server "redis-1" is down
+    And the retry timeout for the redis master check is reached
+    Then a system notification for "redis-1" not being available should be sent
+    And the role of redis server "redis-2" should be "master"
+    And the redis master file of the redis configuration server should contain "redis-2"
+    And the redis master of "rc-client-1" should be "redis-2"
+    And the redis master of "rc-client-2" should be "redis-2"
+    And the redis master of the beetle handler should be "redis-2"
+    And a system notification for switching from "redis-1" to "redis-2" should be sent
+    Given a redis server "redis-1" exists as master
+    Then the role of redis server "redis-1" should be "slave"
+    And the redis server "redis-1" is a slave of "redis-2"
+    And the redis server "redis-3" is a slave of "redis-2"
+
   Scenario: Successful single redis master switch with multiple failover sets
     Given a redis server "redis-3" exists as master
     And a redis server "redis-4" exists as slave of "redis-3"

data/features/step_definitions/redis_auto_failover_steps.rb

@@ -1,8 +1,9 @@
 Given /^consul state has been cleared$/ do
+  consul_host = ENV["CONSUL_HOST"] || "localhost:8500"
   system "killall beetle beetle_handler >/dev/null 2>/dev/null"
-  system "curl --silent --request PUT http://localhost:8500/v1/kv/apps/beetle/config/ >/dev/null"
-  system "curl --silent --request PUT http://localhost:8500/v1/kv/shared/config/ >/dev/null"
-  system "curl --silent --request DELETE http://localhost:8500/v1/kv/apps/beetle/state/redis_master_file_content >/dev/null"
+  system "curl --silent --request PUT http://#{consul_host}/v1/kv/apps/beetle/config/ >/dev/null"
+  system "curl --silent --request PUT http://#{consul_host}/v1/kv/shared/config/ >/dev/null"
+  system "curl --silent --request DELETE http://#{consul_host}/v1/kv/apps/beetle/state/redis_master_file_content >/dev/null"
 end
 
 Given /^a redis server "([^\"]*)" exists as master$/ do |redis_name|
@@ -93,7 +94,6 @@ Given /^an old redis master file for "([^\"]*)" with master "([^\"]*)" exists$/
   end
 end
 
-
 Then /^the role of redis server "([^\"]*)" should be "(master|slave)"$/ do |redis_name, role|
   expected_role = false
   10.times do
@@ -103,6 +103,16 @@ Then /^the role of redis server "([^\"]*)" should be "(master|slave)"$/ do |redi
   assert expected_role, "#{redis_name} is not a #{role}"
 end
 
+Then /^the redis server "([^\"]*)" is a slave of "([^\"]*)"$/ do |redis_name, redis_master_name|
+  master = TestDaemons::Redis[redis_master_name].redis
+  slave = TestDaemons::Redis[redis_name].redis
+  3.times do
+    sleep 1
+    break if slave.slave_of?(master.host, master.port)
+  end
+  assert slave.slave_of?(master.host, master.port)
+end
+
 Then /^the redis master of "([^\"]*)" (?:in system "([^"]*)" )?should be "([^\"]*)"$/ do |redis_configuration_client_name, system_name, redis_name|
   system_name ||= "system"
   master_file = redis_master_file(redis_configuration_client_name)
@@ -143,11 +153,21 @@ end
 Then /^the redis master of the beetle handler should be "([^\"]*)"$/ do |redis_name|
   Beetle.config.servers = "127.0.0.1:5672" # rabbitmq
   Beetle.config.logger.level = Logger::INFO
-  client = Beetle::Client.new.configure :auto_delete => true do |config|
-    config.queue(:echo, :lazy => true, :dead_lettering => true)
-    config.message(:echo)
+  redis_master = TestDaemons::Redis[redis_name].ip_with_port
+  response = nil
+  expected_response = ['OK', redis_master]
+  3.times do |i|
+    client = Beetle::Client.new.configure :auto_delete => true do |config|
+      config.queue(:echo, :lazy => true, :dead_lettering => true)
+      config.message(:echo)
+    end
+    t1 = Time.now
+    response = client.rpc(:echo, 'echo')
+    t2 = Time.now
+    # puts "OK,#{redis_master} =?= #{response.join(',')} after #{t2-t1}, attempt #{i+1}"
+    break if expected_response == response
   end
-  assert_match /#{TestDaemons::Redis[redis_name].ip_with_port}/, client.rpc(:echo, 'nil').second
+  assert_equal expected_response, response
 end
 
 Then /^a system notification for "([^\"]*)" not being available should be sent$/ do |redis_name|

data/features/support/test_daemons/redis_configuration_server.rb

@@ -25,9 +25,10 @@ module TestDaemons
 
     def self.daemon_controller
       clients_parameter_string = @@redis_configuration_clients.blank? ? "" : "--client-ids #{@@redis_configuration_clients}"
+      consul_host = ENV["CONSUL_HOST"] || "localhost:8500"
       DaemonController.new(
          :identifier    => "Redis configuration test server",
-         :start_command => "./beetle configuration_server -v -d --redis-master-file #{redis_master_file} --redis-servers '#{@@redis_servers}' #{clients_parameter_string} --redis-master-retry-interval 1 --pid-file #{pid_file} --log-file #{log_file} --redis-failover-confidence-level #{@@confidence_level} --consul http://localhost:8500",
+         :start_command => "./beetle configuration_server -v -d --redis-master-file #{redis_master_file} --redis-servers '#{@@redis_servers}' #{clients_parameter_string} --redis-master-retry-interval 1 --pid-file #{pid_file} --log-file #{log_file} --redis-failover-confidence-level #{@@confidence_level} --consul http://#{consul_host}",
          :ping_command  => lambda{ answers_text_requests? },
          :pid_file      => pid_file,
          :log_file      => log_file,

data/lib/beetle/publisher.rb

@@ -34,7 +34,7 @@ module Beetle
         Bunny::ConnectionError, Bunny::ForcedChannelCloseError, Bunny::ForcedConnectionCloseError,
         Bunny::MessageError, Bunny::ProtocolError, Bunny::ServerDownError, Bunny::UnsubscribeError,
         Bunny::AcknowledgementError, Qrack::BufferOverflowError, Qrack::InvalidTypeError,
-        Errno::EHOSTUNREACH, Errno::ECONNRESET, Timeout::Error
+        Errno::EHOSTUNREACH, Errno::ECONNRESET, Errno::ETIMEDOUT, Timeout::Error
       ]
     end
 
@@ -66,6 +66,7 @@ module Beetle
         logger.debug "Beetle: message sent!"
         published = 1
       rescue *bunny_exceptions => e
+        logger.warn("Beetle: publishing exception #{e} #{e.backtrace[0..4].join("\n")}")
         stop!(e)
         tries -= 1
         # retry same server on receiving the first exception for it (might have been a normal restart)
@@ -98,6 +99,7 @@ module Beetle
           published << @server
           logger.debug "Beetle: message sent (#{published})!"
         rescue *bunny_exceptions => e
+          logger.warn("Beetle: publishing exception #{e} #{e.backtrace[0..4].join("\n")}")
           stop!(e)
           retry if (tries += 1) == 1
           mark_server_dead

data/lib/beetle/version.rb

@@ -1,3 +1,3 @@
 module Beetle
-  VERSION = "3.5.1"
+  VERSION = "3.5.3"
 end

data/test/beetle/amqp_gem_behavior_test.rb

@@ -7,7 +7,7 @@ class AMQPGemBehaviorTest < Minitest::Test
     begin
       exception = nil
       EM.run do
-        AMQP.start(:logging => false) do |connection|
+        AMQP.start(logging: false, host: ENV['RABBITMQ_SERVERS'] || 'localhost') do |connection|
           EM::Timer.new(1){ connection.close { EM.stop }}
           channel = AMQP::Channel.new(connection)
           channel.on_error { puts "woot"}

data/test/beetle/base_test.rb

@@ -26,7 +26,7 @@ module Beetle
     end
 
     test "server should be initialized" do
-      assert_equal @bs.servers.first, @bs.server
+      assert @bs.server
     end
 
     test "current_host should return the hostname of the current server" do

data/test/beetle/client_test.rb

@@ -8,7 +8,7 @@ module Beetle
     end
 
     test "should have a default server" do
-      assert_equal ["localhost:5672"], @client.servers
+      assert !@client.servers.empty?
     end
 
     test "should have no additional subscription servers" do

data/test/beetle/deduplication_store_test.rb

@@ -87,7 +87,7 @@ module Beetle
     private
     def redis_test_master_file(server_string)
       tmp_dir = File.expand_path("../../../tmp", __FILE__)
-      Dir.mkdir(tmp_dir) unless File.exists?(tmp_dir)
+      Dir.mkdir(tmp_dir) unless File.exist?(tmp_dir)
       path = tmp_dir + "/redis-master-for-unit-tests"
       File.open(path, "w"){|f| f.puts server_string}
       path

data/test/beetle/publisher_test.rb

@@ -77,7 +77,9 @@ module Beetle
 
   class PublisherPublishingTest < Minitest::Test
     def setup
-      @client = Client.new
+      @config = Configuration.new
+      @config.servers = ENV['RABBITMQ_SERVERS'].split(',').first if ENV['RABBITMQ_SERVERS']
+      @client = Client.new(@config)
       @pub = Publisher.new(@client)
       @pub.stubs(:bind_queues_for_exchange)
       @client.register_queue("mama", :exchange => "mama-exchange")
@@ -277,6 +279,7 @@ module Beetle
   class PublisherQueueManagementTest < Minitest::Test
     def setup
       @config = Configuration.new
+      @config.servers = ENV['RABBITMQ_SERVERS'] if ENV['RABBITMQ_SERVERS']
       @client = Client.new(@config)
       @pub = Publisher.new(@client)
     end
@@ -305,7 +308,9 @@ module Beetle
       @client.register_queue('test_queue_2', :exchange => 'test_exchange')
       @client.register_queue('test_queue_3', :exchange => 'test_exchange_2')
       queue = mock("queue")
-      queue.expects(:bind).times(3)
+      @pub.expects(:bind_queue!).with(queue, "test_exchange", {:key => "test_queue_1"}).once
+      @pub.expects(:bind_queue!).with(queue, "test_exchange", {:key => "test_queue_2"}).once
+      @pub.expects(:bind_queue!).with(queue, "test_exchange_2", {:key => "test_queue_3"}).once
       @pub.expects(:declare_queue!).returns(queue).times(3)
       @pub.send(:bind_queues_for_exchange, 'test_exchange')
       @pub.send(:bind_queues_for_exchange, 'test_exchange_2')
@@ -315,18 +320,21 @@ module Beetle
       @client.register_queue('test_queue_1', :exchange => 'test_exchange')
       @client.register_queue('test_queue_2', :exchange => 'test_exchange')
       queue = mock("queue")
-      queue.expects(:bind).twice
       @pub.expects(:declare_queue!).returns(queue).twice
+      @pub.expects(:bind_queue!).with(queue, "test_exchange", {:key => "test_queue_1"}).once
+      @pub.expects(:bind_queue!).with(queue, "test_exchange", {:key => "test_queue_2"}).once
       @pub.send(:bind_queues_for_exchange, 'test_exchange')
       @pub.send(:bind_queues_for_exchange, 'test_exchange')
     end
 
     test "should declare queues only once even with many bindings" do
+
       @client.register_queue('test_queue', :exchange => 'test_exchange')
       @client.register_binding('test_queue', :exchange => 'test_exchange', :key => 'sir-message-a-lot')
       queue = mock("queue")
-      queue.expects(:bind).twice
       @pub.expects(:declare_queue!).returns(queue).once
+      @pub.expects(:bind_queue!).with(queue, "test_exchange", {:key => "test_queue"}).once
+      @pub.expects(:bind_queue!).with(queue, "test_exchange", {:key => "sir-message-a-lot"}).once
       @pub.send(:bind_queues_for_exchange, 'test_exchange')
     end
 
@@ -549,10 +557,11 @@ module Beetle
     end
   end
 
-
   class RPCTest < Minitest::Test
     def setup
-      @client = Client.new
+      @config = Configuration.new
+      @config.servers = ENV['RABBITMQ_SERVERS'].split(',').first if ENV['RABBITMQ_SERVERS']
+      @client = Client.new(@config)
       @pub = Publisher.new(@client)
       @client.register_message(:test, :exchange => :some_exchange)
     end

data/test/beetle/subscriber_test.rb

@@ -52,7 +52,9 @@ module Beetle
 
   class SubscriberPauseAndResumeTest < Minitest::Test
     def setup
-      @client = Client.new
+      @config = Configuration.new
+      @config.servers = "localhost:5672"
+      @client = Client.new(@config)
       @sub = @client.send(:subscriber)
       @sub.servers << "localhost:7777"
       @server1, @server2 = @sub.servers
@@ -342,7 +344,9 @@ module Beetle
 
   class SubscriptionTest < Minitest::Test
     def setup
-      @client = Client.new
+      @config = Configuration.new
+      @config.servers = "locahost:5672"
+      @client = Client.new(@config)
       @sub = @client.send(:subscriber)
     end
 

data/test/test_helper.rb

@@ -27,12 +27,14 @@ end
 I18n.enforce_available_locales = false
 
 Beetle.config.logger = Logger.new(File.dirname(__FILE__) + '/../test.log')
-if `docker inspect beetle-redis-master -f '{{.State.Status}}'`.chomp == "running"
-  Beetle.config.redis_server = "localhost:6370"
-  Beetle.config.redis_servers = "localhost:6370,localhost:6380"
+Beetle.config.servers = ENV["RABBITMQ_SERVERS"] || "localhost:5672"
+
+if system('docker -v >/dev/null') && `docker inspect beetle-redis-master -f '{{.State.Status}}'`.chomp == "running"
+  Beetle.config.redis_server = ENV["REDIS_SERVER"] || "localhost:6370"
+  Beetle.config.redis_servers = ENV["REDIS_SERVERS"] || "localhost:6370,localhost:6380"
 else
-  Beetle.config.redis_server = "localhost:6379"
-  Beetle.config.redis_servers = "localhost:6379,localhost:6380"
+  Beetle.config.redis_server = ENV["REDIS_SERVER"] || "localhost:6379"
+  Beetle.config.redis_servers = ENV["REDIS_SERVERS"] || "localhost:6379,localhost:6380"
 end
 
 def header_with_params(opts = {})
@@ -43,7 +45,6 @@ def header_with_params(opts = {})
   header
 end
 
-
 def redis_stub(name, opts = {})
   default_port = opts['port'] || "1234"
   default_host = opts['host'] || "foo"
@@ -51,6 +52,6 @@ def redis_stub(name, opts = {})
   stub(name, opts)
 end
 
-if `docker inspect beetle-mysql -f '{{.State.Status}}'`.chomp == "running"
+if system('docker -v >/dev/null') && `docker inspect beetle-mysql -f '{{.State.Status}}'`.chomp == "running"
   ENV['MYSQL_PORT'] = '6612'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: beetle
 version: !ruby/object:Gem::Version
-  version: 3.5.1
+  version: 3.5.3
 platform: ruby
 authors:
 - Stefan Kaes
@@ -12,7 +12,7 @@ authors:
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-06-01 00:00:00.000000000 Z
+date: 2022-02-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bunny
@@ -225,49 +225,77 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '13.0'
 - !ruby/object:Gem::Dependency
-  name: rdoc
+  name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '4.0'
+        version: '0.15'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '4.0'
+        version: '0.15'
 - !ruby/object:Gem::Dependency
-  name: simplecov
+  name: webmock
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.15'
+        version: '3.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.15'
+        version: '3.0'
 - !ruby/object:Gem::Dependency
-  name: webmock
+  name: websocket-eventmachine-client
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: '0'
 - !ruby/object:Gem::Dependency
-  name: websocket-eventmachine-client
+  name: yard
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: redcarpet
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: github-markup
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -285,19 +313,11 @@ email: opensource@xing.com
 executables: []
 extensions: []
 extra_rdoc_files:
-- RELEASE_NOTES.rdoc
-- examples/README.rdoc
-- REDIS_AUTO_FAILOVER.rdoc
-- README.rdoc
 - MIT-LICENSE
 files:
 - MIT-LICENSE
-- README.rdoc
-- REDIS_AUTO_FAILOVER.rdoc
-- RELEASE_NOTES.rdoc
 - Rakefile
 - beetle.gemspec
-- examples/README.rdoc
 - examples/attempts.rb
 - examples/attempts_with_dead_letter_and_exponential_backoff.rb
 - examples/attempts_with_exponential_backoff.rb
@@ -378,24 +398,24 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: 1.3.7
 requirements: []
-rubygems_version: 3.2.16
+rubygems_version: 3.3.4
 signing_key:
 specification_version: 3
 summary: High Availability AMQP Messaging with Redundant Queues
 test_files:
-- test/beetle_test.rb
-- test/beetle/client_test.rb
 - test/beetle/amqp_gem_behavior_test.rb
-- test/beetle/deduplication_store_test.rb
-- test/beetle/queue_properties_test.rb
-- test/beetle/handler_test.rb
+- test/beetle/base_test.rb
 - test/beetle/beetle_test.rb
+- test/beetle/client_test.rb
 - test/beetle/configuration_test.rb
-- test/beetle/subscriber_test.rb
+- test/beetle/deduplication_store_test.rb
+- test/beetle/handler_test.rb
 - test/beetle/message/settings_test.rb
-- test/beetle/redis_ext_test.rb
 - test/beetle/message_test.rb
 - test/beetle/publisher_test.rb
+- test/beetle/queue_properties_test.rb
 - test/beetle/r_c_test.rb
-- test/beetle/base_test.rb
+- test/beetle/redis_ext_test.rb
+- test/beetle/subscriber_test.rb
+- test/beetle_test.rb
 - test/test_helper.rb

data/README.rdoc

@@ -1,233 +0,0 @@
-= Beetle
-
-High Availability AMQP Messaging with Redundant Queues
-
-== About
-
-Beetle grew out of a project to improve an existing ActiveMQ based messaging
-infrastructure. It offers the following features:
-
-* High Availability (by using multiple message broker instances)
-* Redundancy (by replicating queues)
-* Simple client API (by encapsulating the publishing/ deduplication logic)
-
-More information can be found on the {project website}[http://xing.github.com/beetle].
-
-== Release notes
-
-See {RELEASE_NOTES.rdoc}[https://github.com/xing/beetle/blob/master/RELEASE_NOTES.rdoc]
-
-== Usage
-
-=== Configuration
-    # configure machines
-
-    Beetle.config do |config|
-      config.servers = "broker1:5672, broker2:5672"
-      config.redis_server = "redis1:6379"
-    end
-
-    # instantiate a beetle client
-
-    b = Beetle::Client.new
-
-    # configure exchanges, queues, bindings, messages and handlers
-
-    b.configure do
-      queue :test
-      message :test
-      handler(:test) { |message| puts message.data }
-    end
-
-=== Publishing
-    b.publish :test, "I'm a test message"
-
-=== Subscribing
-    b.listen_queues
-
-=== Examples
-
-Beetle ships with a number of {example scripts}[http://github.com/xing/beetle/tree/master/examples/].
-
-The top level Rakefile comes with targets to start several RabbitMQ and redis instances
-locally. Make sure the corresponding binaries are in your search path. Open four new shell
-windows and execute the following commands:
-
-    rake rabbit:start1
-    rake rabbit:start2
-    rake redis:start:master
-    rake redis:start:slave
-
-== Prerequisites
-
-To set up a redundant messaging system you will need
-* at least 2 AMQP servers (we use {RabbitMQ}[http://www.rabbitmq.com/])
-* at least one {Redis}[http://github.com/antirez/redis] server (better are two in a master/slave setup, see REDIS_AUTO_FAILOVER.rdoc)
-
-== Test environment
-
-For testing purposes, you will need a MySQL database with the database
-`beetle_test` created. This is needed to test special cases in which
-Beetle handles the connection with ActiveRecord:
-
-     mysql -e 'create database beetle_test;'
-
-You also need a Redis instance running. The default configuration of Redis will work:
-
-    redis-server
-
-If you want to run the integration tests you need GO installed and you
-will need to build the beetle binary. We provide a Makefile for this
-purpose, so simply running
-
-    make
-
-should suffice.
-
-== Gem Dependencies
-
-At runtime, Beetle will use
-* {bunny}[http://github.com/ruby-amqp/bunny]
-* {redis}[http://github.com/redis/redis-rb]
-* {amqp}[http://github.com/ruby-amqp/amqp]
-  (which is based on {eventmachine}[http://github.com/eventmachine/eventmachine])
-* {daemons}[http://daemons.rubyforge.org/]
-* {activesupport}[https://github.com/rails/rails/tree/master/activesupport]
-
-For development, you'll need
-* {mocha}[http://github.com/floehopper/mocha]
-* {cucumber}[http://github.com/aslakhellesoy/cucumber]
-* {daemon_controller}[http://github.com/FooBarWidget/daemon_controller]
-* {consul}[https://www.consul.io/downloads.html]
-
-For tests, you'll need
-* {activerecord}[https://github.com/rails/rails/tree/master/activerecord]
-* {mysql2}[https://github.com/brianmario/mysql2/]
-
-Dependencies are managed by bundler.
-
-== Authors
-
-{Stefan Kaes}[http://github.com/skaes],
-{Pascal Friederich}[http://github.com/paukul],
-{Ali Jelveh}[http://github.com/dudemeister],
-{Bjoern Rochel}[http://github.com/bjro] and
-{Sebastian Roebke}[http://github.com/boosty].
-
-You can find out more about our work on our {dev blog}[http://devblog.xing.com].
-
-Copyright (c) 2010-2019 {XING AG}[http://www.xing.com/]
-
-Released under the MIT license. For full details see MIT-LICENSE included in this
-distribution.
-
-== Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Hack along and test your code.
-4. Commit your changes (`git commit -am 'Add some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Create new Pull Request
-
-Don't increase the gem version in your pull requests. It will be done after merging the request,
-to allow merging of pull requests in a flexible order.
-
-== Compiling beetle and running tests
-
-In order to execute the unit tests, you need Ruby, a running rabbitmq server, a running
-redis-server, a running mysql server and a runnning consul server.
-
-In addition, beetle ships with a cucumber feature to test the automatic redis failover as
-an integration test. For this you need a recent Go installation in order to compile the
-beetle go binary. Just invoke `make` in the top level directory.
-
-There are two ways to start the required test dependencies: using `docker-compose` or
-starting the services manually.
-
-=== Testing with docker-compose
-
-Open a separate terminal window and run
-
-     docker-compose pull
-
-followed by
-
-     docker-compose up
-
-This will start mysql, two redis servers, two RabbitMQ instances and a single consul
-development node.
-
-Note: make sure to wait until all services are properly started.
-
-
-== Tesing with  locally installed services
-
-The top level Rakefile comes with targets to start several RabbitMQ instances locally.
-Make sure the corresponding binaries are in your search path. Open three shell windows and
-execute the following command:
-
-    rake rabbit:start1
-
-and
-
-   rake redis:start:master
-
-as well as
-
-   rake consul:start
-
-Then you can run the cucumber feature by running:
-
-    cucumber
-
-or
-
-    rake cucumber
-
-Note: Cucumber will automatically run after the unit tests when you run `rake` without
-arguments.
-
-
-== How to release a new gem version
-
-Update RELEASE_NOTES.rdoc!
-
-We use {semantic versioning}[http://semver.org/] and create a git tag
-for each release.
-
-Edit `lib/beetle/version.rb` and
-`go/src/github.com/xing/beetle/version.go` to set the new version
-number (`Major.Minor.Patch`).
-
-In short (see {semver.org}[http://semver.org] for details):
-
-* *Major* version MUST be incremented if any backwards incompatible changes
-  are introduced to the public API.
-* *Minor* version MUST be incremented if new, backwards compatible functionality
-  is introduced to the public API. It MUST be incremented if any public API
-  functionality is marked as deprecated.
-* *Patch* version MUST be incremented if only backwards compatible bug fixes
-  are introduced.
-
-Then use `rake release` which will create the git tag and upload the
-gem to github.com:
-
-    bundle exec rake release
-
-The generated gem is located in the `pkg/` directory.
-
-In order to build go binaries and upload the docker container with the
-beetle GO binary to docker hub, run
-
-    make release
-
-This will upload the go binaries to https://github.com/xing/beetle/
-and push the beetle container to
-https://hub.docker.com/r/xingarchitects/gobeetle/.
-
-Run
-
-    make tag push TAG=X.X.X
-
-to tag and push the container with a specific version number.

data/REDIS_AUTO_FAILOVER.rdoc

@@ -1,116 +0,0 @@
-= Automatic Redis Failover for Beetle
-
-== Introduction
-
-Redis is used as the persistence layer in the AMQP message deduplication
-process. Because it is such a critical piece in our infrastructure, it is
-essential that a failure of this service is as unlikely as possible. As our
-AMQP workers are working in a highly distributed manner, all accessing the same
-Redis server, a automatic failover to another Redis server has to be very
-defensive and ensure that every worker in the system will switch to the new
-server at the same time. If the new server would not get accepted from every
-worker, a switch would not be possible. This ensures that even in the case of a
-partitioned network it is impossible that two different workers use two
-different Redis servers for message deduplication.
-
-== Our goals
-
-* opt-in, no need to use the redis-failover solution
-* no single point of failure
-* automatic switch in case of redis-master failure
-* switch should not cause inconsistent data on the redis servers
-* workers should be able to determine the current redis-master without asking
-  another process (as long as the redis servers are working)
-
-== How it works
-
-To ensure consistency, a service (the Redis Configuration Server - RCS) is
-constantly checking the availability and configuration of the currently
-configured Redis master server. If this service detects that the Redis master
-is no longer available, it tries to find an alternative server (one of the
-slaves) which could be promoted to be the new Redis master.
-
-On every worker server runs another daemon, the Redis Configuration Client
-(RCC) which listens to messages sent by the RCS.
-
-If the RCS finds another potential Redis Master, it sends out a message to see
-if all known RCCs are still available (once again to eliminate the risk of a
-partitioned network) and if they agree to the master switch.
-
-If all RCCs have answered to that message, the RCS sends out a message which
-tells the RCCs to invalidate the current master.
-
-This happens by deleting the contents of a special file which is used
-by the workers to store the current Redis master (the content of that file is
-the hostname:port of the currently active Redis master). By doing that, it is
-ensured that no operations are done to the old Redis master server anymore, because the
-AMQP workers check this file's mtime and reads its contents in case that the
-file changed, before every Redis operation. When the file has been emptied, the
-RCCs respond to the "invalidate" message of the RCS. When all RCCs have
-responded, the RCS knows for sure that it is safe to switch the Redis master
-now. It sends a "reconfigure" message with the new Redis master hostname:port
-to the RCCs, which then write that value into their redis master file.
-
-Additionally, the RCS sends reconfigure messages with the current Redis master
-periodically, to allow new RCCs to pick up the current master. Plus it turns
-all other redis servers into slaves of the current master.
-
-=== Prerequisites
-
-* one redis-configuration-server process ("RCS", on one server), one redis-configuration-client process ("RCC") on every worker server
-* the RCS knows about all possible RCCs using a list of client ids
-* the RCS and RCCs exchange messages via a "system queue"
-
-=== Flow of actions
-
-* on startup, an RCC can consult its redis master file to determine the current master without the help of the RCS by checking that it's still a master (or wait for the periodic reconfigure message with the current master from the RCS)
-* when the RCS finds the master to be down, it will retry a couple of times before starting a reconfiguration round
-* the RCS sends all RCCs a "ping" message to check if every client is there and able to answer
-* the RCCs acknowledge via a "pong" message if they can confirm the current master to be unavailable
-* the RCS waits for *all* RCCs to reply via pong
-* the RCS tells all RCCs to stop using the master by sending an "invalidate" message
-* the RCCs acknowledge via an "invalidated" message if they can still confirm the current master to be unavailable
-* the RCS waits for *all* RCCs to acknowledge the invalidation
-* the RCS promotes the former slave to become the new master (by sending SLAVEOF no one)
-* the RCS sends a "reconfigure" message containing the new master to every RCC
-* the RCCs write the new master to their redis master file
-
-=== Configuration
-
-See Beetle::Configuration for setting redis configuration server and client options.
-
-Please note:
-Beetle::Configuration#redis_server must be a file path (not a redis host:port string) to use the redis failover. The RCS and RCCs store the current redis master in that file, and the handlers read from it.
-
-== How to use it
-
-This example uses two worker servers, identified by rcc-1 and rcc-2.
-
-Please note:
-All command line options can also be given as a yaml configuration file via the --config-file option.
-
-=== On one server
-
-Start the Redis Configuration Server:
-
-  beetle configuration_server --redis-servers redis-1:6379,redis-2:6379 --client-ids rcc-1,rcc-2
-
-Get help for server options:
-
-  beetle configuration_server -h
-
-=== On every worker server
-
-Start the Redis Configuration Client:
-
-On first worker server:
-
-  beetle configuration_client --client-id rcc-1
-
-On second worker server:
-
-  beetle configuration_client --client-id rcc-2
-
-Get help for client options:
-
-  beetle configuration_client -h

data/RELEASE_NOTES.rdoc

@@ -1,383 +0,0 @@
-= Release Notes
-
-== Version 3.5.1
-*  remove blank entries from server list strings
-*  make sure not to subscribe to any server twice
-
-== Version 3.5.0
-* expose publisher method to setup queues/policies ahead of use
-
-== Version 3.4.3
-* optimize declaration of queues with many bindings
-
-== Version 3.4.2
-* Updated amq-protocol gem to version 2.3.2.
-* Fixed a rare race condition on message handler timeouts.
-
-== Version 3.4.1
-* Updated amq-protocol gem to version 2.3.1.
-
-== Version 3.4.0
-* Require redis gem version 4.2.1. This version changes the exists to check for the
-  existence of multiple keys, return the number of keys in the list that exist. This
-  requires at least redis gem version 4.2.0, but 4.2.1 contains a bug fix for said
-  command.
-
-== Version 3.3.12
-* Support queue level declaration of dead letter queue message TTL.
-
-== Version 3.3.11
-* Fixed that dead lettering only works correctly with global config option.
-
-== Version 3.3.10
-* Support configuring RabbitMQ write timeout.
-
-== Version 3.3.9
-* Reduce the number of queue policies created on the servers by allowing
-  the spefication of a default broker policy. You need to install the
-  default policy with a priority of zero to match all queues ever
-  created. This feature is optional.
-
-== Version 3.3.8
-* Avoid needless put call when updating queue policies.
-  It seems the additional call to get the current definition of a policy
-  is to be preferred over relying on the idempotency of the PUT call.
-  This helps when adding a new fresh server to a beetle cluster: import
-  the definitions of one of the existing nodes on the fresh node before
-  actually adding it to the list of servers in the client's beetle config..
-
-== Version 3.3.7
-* Increased default http api read timeout to handle large server better.
-
-== Version 3.3.6
-* Fixed a redis connection leak in gobeetle.
-
-== Version 3.3.5
-* Support synchronous queue policy creation.
-
-== Version 3.3.4
-* Track publishing policy options metrics.
-
-== Version 3.3.3
-* Broken.
-
-== Version 3.3.2
-* Changed order of queue policy application to avoid ahead of line blocking in dead letter
-  queues.
-
-== Version 3.3.1
-* It seems that there is a certain preference on connection level when
-  selecting the next message to process. We try to protect against
-  such bias by connecting in random order.
-
-== Version 3.3.0
-* protect against duplicate handler execution by keeping the status of
-  handler exectution for both redundant and non-redundant messages in
-  the dedup store for a configurable time window. The config option
-  is named redis_status_key_expiry_interval. Note that this will
-  significantly increase the cpu load and memory usage of the Redis
-  server for applications using a large number of non-redundant
-  messages. This feature is turned off by default, but we will
-  activate it with the next major release (4.0.0).
-
-== Version 3.2.0
-* added currently processed message to the handler pre-processing step
-
-== Version 3.1.0
-* added more debug log statements
-* added new callbacks on class Beetle::Handler:
-  * pre_process is called before any message processing commences
-  * post_process is called after all processing has been completed
-  these handlers can be used for logging purposes (such as logjam
-  integration)
-
-== Version 3.0.0
-
-* provide client method to setup queues and queue policies.
-  Setting up queue policies on demand in publisher and subscriber is OK
-  for a small number of queues, publishers and subscribers. But the HTTP
-  API of RabbitMQ doesn't scale all that well, so that a large number
-  of HTTP calls to set up queue policies can in fact crash a server.
-* allow queue mode specification and dead lettering specification on a
-  per queue basis.
-* change policy setup to be asynchronous, on demand in publisher and
-  consumer. Users have to run a processors to listen to messages and
-  call setup_queue_policies! with the parses JSON paylod of the
-  message.
-* store redis gc stats in redis and display them in the configuration
-  server web UI
-* config server: store current master server in consul, if consul
-  config has been provided.
-* config server: server correctly updates configured client ids when
-  they change in consul.
-* don't create dead letter queues when using the trace functionality
-* make sure to clean dedup store when ack_count is larger than 2
-* added dump_expiries command to beetle to dump dediplication store
-  expiry times.
-* added delete_queue_keys command to beetle to allow deletion of
-  excess dedup store entries for a given queue.
-
-== Version 2.3.2
-* config server: fixed a race condition when accessing server state.
-  HTTP requests run in threads separate from the server dispatcher
-  thread and thus can cause race conditions/crashes when accessing
-  server state. Solved this by adding a closure evaluator to the
-  dispatcher.
-
-== Version 2.3.1
-* updated amqp and amq-protocol requirements in ruby client.
-* fixed that a change in consul endpoint was not properly handled by
-  the beetle configuration client.
-
-== Version 2.3.0
-* redis failover: support multiple redis failover instances. This has
-  required a change in the redis master file format. The master file
-  content is now either the old format (host:port) for systems using a
-  single redis failover system or a mapping from system names to
-  host:port combinations. For example,
-  "system1/master1:6379\nsystem2/master" specifies to systems with
-  their corresponding redis masters. Beetle client uses the configured
-  system name to tind the master it should use.
-* support lazy queues: setting :lazy_quques_enabled on the beetle
-  cofiguration will enable queue_mode: "lazy" for all queues of
-  declared on the beetle client.
-* improved calculation of channel close an connection disconnect
-  timeouts for beetle publisher to avoid warnings in RabbitMQ logs.
-* use SecureRandom.uuid instead of UUID4R::uuid(4) if UUID4R cannot
-  be loaded.
-
-== Version 2.2.4
-* redis failover: prevent starting a new master switch while one is running
-
-== Version 2.2.3
-* redis failover: server logs errors when redis oparations fail
-
-== Version 2.2.2
-
-* Reset redis configuration server state when master becomes available during
-  pinging or invalidating.  Unlike the former ruby implementation, the go code
-  continues checking redis availability during pinging or invalidating. However,
-  the code did not reset state properly, leading the UI to display 'switch in
-  progress' when in fact there wasn't.
-
-== Version 2.2.1
-* Subscriber exits with meaningful error log on possible authentication failures.
-
-== Version 2.2.0
-
-* Support specifying a whitelist of retriable exceptions when registering a
-  message handler. Exceptions which are not on the list will be regarded as
-  irrecoverable failures.
-
-== Version 2.1.2
-
-* Fixed that redis key GC would never complete when a key scheduled
-  for GC was deleted by a consumer before the collector could retrieve
-  its expiry date.
-* Fixed tha redis key GC would crash on malformed keys.
-* Added method to collect keys specified in a file.
-
-
-== Version 2.1.1
-
-* Support redis failover with less than 100% acknowlegment from failover clients.
-
-== Version 2.1.0
-
-* Support exponential backoff when delaying messages using 'max_delay: int' option.
-
-== Version 2.0.2
-
-* fixed incorrect computation of responsiveness threshold in
-  configuration server
-
-== Version 2.0.1
-
-* fix for beetle command not geting stuck when connecting to
-  configuration server
-* configuration server displays last seen times in a human readable format
-
-== Version 2.0.0
-
-* beetle command has been rewritten in Go
-* garbage collecting redis keys now uses the redis SCAN command
-
-== Version 1.0.4
-
-* use amqp protocol version 0.9 by default for publishers
-
-== Version 1.0.3
-
-* fixed that publisher did not allow specifying message properties
-
-== Version 1.0.2
-
-* relax hiredis requirements to >= 0.4.5
-
-== Version 1.0.1
-
-* don't try to connect on publisher shutdown
-
-== Version 1.0.0
-
-* introduced semantic versioning
-* upgraded gems used for devloping beetle
-* upgraded amqp gem to version 1.6.0 and amq-protocol to 2.0.1
-* relaxed requirements on redis and hiredis versions
-* support setting prefetch count for subscriber
-
-== Version 0.4.12
-
-* Don't log warnings when publishing redundantly and only
-  one server has been configured
-
-== Version 0.4.11
-
-* Automatically close open publisher sockets at program exit
-
-== Version 0.4.10
-
-* Publisher handles nil and symbols as values in headers correctly
-
-== Version 0.4.9
-
-* Allow redis_configuration_client to run in the foreground (useful
-  for docker)
-
-== Version 0.4.8
-
-* unseen clients need to be an array
-
-== Version 0.4.7
-
-* list clients which have never sent a ping in the failover server UI
-
-== Version 0.4.6
-
-* Publish activesupport notifications to support performance measurements
-
-== Version 0.4.5
-
-* Starting mutliple redis failover clients is now prohibited by
-  default. This behavior can be overriden using
-  "beetle configuration_client start -- --multiple"
-
-== Version 0.4.4
-
-* added command to show beetle version: "beetle --version"
-* configuration server tracks ids of unknown clients
-* configuration clients now sends heartbeats
-* configuration server tracks last seen times of clients, based on heartbeat
-
-== Version 0.4.3
-
-* fixed a race condition which could lead to duplicate message processing
-* fixed eventmachine shutdown sequence problem, which led to ACKs
-  occasionally being lost due to writing to a closed socket, which in
-  turn caused messages to be processed twice
-* stop_listening now always triggers the subscribe shutdown sequence
-  via a eventmachine timer callback, if the eventmachine reactor is running
-
-== Version 0.4.2
-
-* Fail hard on missing master file
-* Set message timestamp header
-
-== Version 0.4.1
-
-* Require newer bunny version (0.7.10) to fix publishing of messages larger than frame_max
-
-== Version 0.4.0
-
-* Added optional dead lettering feature to mimic RabbitMQ 2.x requeueing behaviour on RabbitMQ 3.x
-
-== Version 0.3.14
-
-* switched message id generation to use v4 uuids
-
-== Version 0.3.0
-
-* redis master file contents now correctly reflects the state of the running configuration server
-* allow accelerating master switch via POST to redis configuration server
-* embedded http server into the redis configuration server (port 8080)
-* fixed a problem with redis shutdown command
-* upgraded to redis 2.2.2
-* upgraded to amqp gem version 0.8 line
-* use hiredis as the redis backend, which overcomes lack of proper time-outs in the "generic" redis-rb
-  gem for Ruby 1.9
-* use fully qualified hostnames to identify redis configuration clients
-
-== Version 0.2.9.8
-
-* since version 2.0, RabbitMQ supports Basic.reject(:requeue => true). we use it now too,
-  because it enhances performance of message processors. this means of course, you can
-  only use beetle gem versions >= 0.2.9.8 if your rabbitmq brokers are at least version 2.0.
-* publishing timeout defaults to 0 to avoid extreme message loss in some cases
-
-
-== Version 0.2.9.7
-
-* use new bunny_ext gem and allow specification of global publishing timeouts
-* registering a message now automatically registers the corresponding exchange
-* don't try to bind queues for an exchange hich has no queue
-* ruby 1.9.2 compatibility fixes
-
-== Version 0.2.9
-
-* Beetle::Client now raises an exception when it fails to publish a message to at least 1 RabbitMQ server
-* Subscribers are now stopped cleanly to avoid 'closed abruptly' messages in the RabbitMQ server log
-
-== Version 0.2.6
-
-* Set dependency on ActiveSupport to 2.3.x since it ain't compatible to version 3.x yet
-* Publishers catch a wider range (all?) of possible exceptions when publishing messages
-* Redis Configuration Servers detect and warn when unknown Redis Configuration Clients connect
-
-== Version 0.2.5
-
-Added missing files to gem and rdoc
-
-== Version 0.2.4
-
-Log and send a system notification when pong message from unknown client received.
-
-== Version 0.2.2
-
-Patch release which upgrades to redis-rb 2.0.4. This enables us to drop our redis monkey
-patch which enabled connection timeouts for earlier redis versions. Note that earlier
-Beetle versions are not compatible with redis 2.0.4.
-
-== Version 0.2.1
-
-Improved error message when no rabbitmq broker is available.
-
-== Version 0.2
-
-This version adds support for automatic redis deduplication store failover (see separate
-file REDIS_AUTO_FAILOVER.rdoc).
-
-=== User visible changes
-
-* it's possible to register auto deleted queues and exchanges
-* Beetle::Client#configure returns self in order to simplify client setup
-* it's possible to trace specific messages (see Beetle::Client#trace)
-* default message handler timeout is 10 minutes now
-* system wide configuration values can be specified via a yml formatted configuration
-  file (Beetle::Configuration#config_file)
-* the config value redis_server specifies either a single server or a file path (used
-  by the automatic redis failover logic)
-
-=== Fugs Bixed
-
-* handle active_support seconds notation for handler timeouts correctly
-* error handler was erroneously called for expired messages
-* subscribers would block when some non beetle process posts an undecodable message
-
-=== Gem Dependency Changes
-
-* redis needs to be at least version 2.0.3
-* we make use of the SystemTimer gem for ruby 1.8.7
-
-== Version 0.1
-
-Initial Release

data/examples/README.rdoc

@@ -1,12 +0,0 @@
-=== Examples
-
-Beetle ships with a number of {example scripts}[http://github.com/xing/beetle/tree/master/examples/].
-
-The top level Rakefile comes with targets to start several RabbitMQ and redis instances
-locally. Make sure the corresponding binaries are in your search path. Open four new shell
-windows and execute the following commands:
-
-    rake rabbit:start1
-    rake rabbit:start2
-    rake redis:start:master
-    rake redis:start:slave