Project

General

Profile

Feature #375

Investigate current issues with RabbitMQ

Added by Tanvi Marballi over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
% Done:

0%

Estimated Time:
1.00
Deployment type:
AppScale - self deployed

History

#1 Updated by Graziano Obertelli about 4 years ago

  • Status changed from New to In Progress
  • Assignee changed from Tanvi Marballi to Graziano Obertelli
  • Target version changed from 3.2.0 to 3.3

After some investigation we have the following:
- rabbitMQ doesn't like to have a lot of nodes in the cluster, a small number is best
- rabbitMQ can use aliases in hostname, not only real hostnames
- the current setup doesn't replicate the queues.

#2 Updated by Graziano Obertelli almost 4 years ago

  • Status changed from In Progress to Closed

For 3.3 we changed the way taskqueue nodes operates, to allow for a smaller number of nodes (ie small rabbitmq cluster), added the replication of queues, and changed the way rabbitmq starts.

Also available in: Atom PDF