StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16834406
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-30T11:00:18.030
FavoriteCount
0
LastActivityDate
2013-05-30T11:00:18.030
LastEditDate
LastEditorUserId
0
OwnerUserId
2296812
ParentId
16830888
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I haven't seen any clients that do connection pooling for AMQP/RabbitMQ. AMQP handles multiple publishers/consumers in a single process with channels and some clients make that easy to use but don't seem to handle automated failover of nodes using a connection pool. In a cluster there is no need to connect to all nodes in the cluster, consume and publish operations will be correctly routed within the cluster. For consuming trying to manage either single or multiple processes with multiple subscriptions (at least one consume for each connection) has never been the highest priority for me. With multiple processes consuming, each randomly connecting to RabbitMQ, you will be able to maintain availability should one of the RabbitMQ nodes fail. Publishers in long-lived connections are easily able to reconnect if a failure is detected causing less than a second of disruption, small enough in anything I've worked on to not be a problem. From a few years of usage I would say that reconnecting to a new host is the simpler problem during a failover with the difficult problem being managing the state within your application in regards to existing AMQP connections. In practice I've just kept a list of the hosts available and pick the next one for each new connection. Any time the connection closes just pick a new host and try again. It does mean a short time where you cannot publish and may be more difficult if you have to constantly make new connections in PHP. Due to <a href="http://www.rabbitmq.com/memory.html" rel="nofollow">flow control</a> TCP load balancers may be more trouble then they are worth. The TCP back pressure may not make it through the LB causing publishers to publish faster than RabbitMQ can handle. In unscientific tests I've had more issues with RabbitMQ stability when it was behind a load balancer then when clients connected directly. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORabbitMQ client load balancing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPhilip Cristiano
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.