Erlang/OTP Forums

Author Message

<  RabbitMQ mailing list  ~  Rabbit-MQ crashing

Guest
Posted: Sun Jan 03, 2010 5:06 pm Reply with quote
Guest
We're experiencing this problem as well. Just from reading the list
it seems that the new persister stuff committed around 12/1 is
supposed to fix it.

I'm curious:

- has this bug indeed been fixed?
- is the code somewhere past bleeding edge? Would you consider it to be stable?
- please excuse my ignorance, but is there any bug or ticket url that
I can follow to keep track of the fix / when it's been released / etc
?

Regards,
Steve

On Thu, Nov 12, 2009 at 6:25 AM, Tony Garnock-Jones <tonyg@lshift.net> wrote:
> Hi Derek,
>
> (Replying here as well for the archive)
>
> Derek Burdick wrote:
>> I have a durable, fanout exchange and queue.
Guest
Posted: Wed Jan 06, 2010 11:48 am Reply with quote
Guest
Hi Steve,

On Sun, Jan 03, 2010 at 09:05:55AM -0800, Steve Conover wrote:
> We're experiencing this problem as well. Just from reading the list
> it seems that the new persister stuff committed around 12/1 is
> supposed to fix it.
>
> I'm curious:
>
> - has this bug indeed been fixed?
> - is the code somewhere past bleeding edge? Would you consider it to be stable?
> - please excuse my ignorance, but is there any bug or ticket url that
> I can follow to keep track of the fix / when it's been released / etc
> ?

The new persister is available only from our mercurial repository at
http://hg.rabbitmq.com/rabbitmq-server

You should be on branch bug21673

The code there is a substantial reworking of Rabbit's persister layer -
about a third of the code is different from that released in 1.7.0.
Several people on this list are using bug21673 successfully, but do from
time to time report bugs (which are usually fixed within a matter of
hours!).

Several of my blog posts and presentations that I've given on the new
persister cover the various issues of the current persister that we're
working to solve. Start at
http://www.lshift.net/blog/category/lshift-sw/rabbitmq and look at the
posts by me (not to say the others aren't interesting, just that they
don't cover the new persister!).

We don't really consider anything to be "stable". 1.5.4 was, IIRC,
marked "stable", but I think that's the only release we've ever
indicated as such. 1.7.0 is not marked "stable" because quite a lot of
code changed between 1.6.1 and 1.7.0. However, in reality, I don't know
if anyone has come across any bugs at all in 1.7.0 (which isn't to say
that we haven't, only to say that these bugs haven't been spotted by
others).

Some of the code in bug21673 has been through QA, some of it hasn't. In
reality, that code isn't going to appear in a stable release for some
months, but if you're aware of the risks and are happy to accomodate
them then you may well find bug21673 to be good enough for your
purposes. However, if/when it breaks, you get to keep all the pieces,
and we don't restrain ourselves from introducing changes which mean that
it will crash on startup if you don't nuke out your existing database.
We do however, very much welcome bug reports.

I hope that's of some use.

Matthew

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist
Guest
Posted: Sat Jan 09, 2010 4:17 pm Reply with quote
Guest
It is, thank you for the update. -Steve

> I hope that's of some use.
>
> Matthew
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss@lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist
wuji
Posted: Tue Aug 14, 2012 6:49 am Reply with quote
User Joined: 10 Aug 2012 Posts: 654
of a U.S. horseracing track denied allegations Monday that that jordan 6 that the chief of Mexico's most violent drug cartel had
a $1 million race so his own horse would win.According win.According imitation designer *beep* win.According to two confidential FBI informants, Zetas leader Miguel Angel
Morales, also known as "40," bragged that he had paid paid jordan 6 olympic 2012 paid the gatekeepers at New Mexico's Ruidoso Downs $10,000 "to
back the horses" competing against his own horse, Mr. Piloto, Piloto, replica designer *beep* Piloto, in the 2010 All American Futurity Race, which Mr.
won.Trevino Morales and 13 other defendants were indicted last week week [h3]imitation designer *beep*[/h3] week for allegedly laundering at least $20 million in cocaine
through horse racing, breeding and training in the U.S. The The [h3]jordan 6s[/h3] The informants' claims were part of an affidavit filed in
of a search warrant for an Oklahoma horse ranch allegedly allegedly [h4]cheap jordans[/h4] allegedly owned by a Zetas front corporation.Shaun Hubbard, general manager
View user's profile Send private message

Display posts from previous:  

All times are GMT
Page 1 of 1
This forum is locked: you cannot post, reply to, or edit topics.

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum