Thanks for you answer Utkarsh, So... it seems that what I see is not what's expected! Since I can confirm this behaviour, I filed a bug report: https://issues.apache.org/jira/browse/BOOKKEEPER-37
Matthieu On Aug 1, 2011, at 7:40 PM, Utkarsh Srivastava wrote: > Hey Matthieu, > > The syncPublish is just a thin wrapper over the asyncPublish method. They > have identical delivery-order guarantees. > > As long as you are calling the sync/async Publish in a well-defined order, > you can expect messages to show up on the client in the same order. If > you've seen examples, where this does not happen, please let us know so that > we can track it as a bug. > > Utkarsh > > On Mon, Aug 1, 2011 at 10:14 AM, Matthieu Morel <[email protected]>wrote: > >> Hi, >> >> I have a question about the ordering of messages in Hedwig when they are >> sent by a client using the "asyncPublish" publish method. >> >> For instance >> M1, M2, M3 >> >> From what I see, messages may be received by Hedwig in a different order: >> M2, M1, M3 >> >> Therefore delivered to subscriber in this order: >> M2, M1, M3 >> >> I was wondering whether this was the expected behaviour? >> >> >> >> Thanks in advance! >> >> Matthieu >> >> >> (Note that I can still ensure that ordering by using the synchronous >> "publish" method (but losing some throughput in that case).) >> >>
