Ask,<div><br></div><div>READ-COMMITED did not seem to work, any other ideas? I don't wish to change my engine to MyISAM =)</div><div><br></div><div>Suhail<br><br><div class="gmail_quote">On Thu, Aug 13, 2009 at 12:46 PM, Jason J. W. Williams <span dir="ltr"><<a href="mailto:jasonjwwilliams@gmail.com">jasonjwwilliams@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Depending on your requirements MyISAM can be a better choice. The<br>
table-wide locks are lightning fast, and can work better in a high<br>
concurrency insert environment than InnoDB. But you lose ACID so you<br>
have to make sure you're replicating to another box for data<br>
integrity.<br>
<font color="#888888"><br>
-J<br>
</font><div><div></div><div class="h5"><br>
On Thu, Aug 13, 2009 at 1:25 PM, Suhail Doshi<<a href="mailto:digitalwarfare@gmail.com">digitalwarfare@gmail.com</a>> wrote:<br>
> Anyone using rabbitmq with lots of consumers along with MySQL and hitting<br>
> dead locks if you run too many consumers, any smart way to deal with that?<br>
> My theory was sharding on some distinct id and sending only some data to<br>
> specific consumers based on an id...<br>
> Ideas? Suggestions?<br>
><br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://mixpanel.com">http://mixpanel.com</a><br>Blog: <a href="http://blog.mixpanel.com">http://blog.mixpanel.com</a><br>
</div>