Questions[message-queuing](server)

I have a Pulsar cluster of 3 machines. Each one running Pulsar broker, Zookeeper and Bookkeeper. I have the following in my broker.conf:

managedLedgerDefaultEnsembleSize=2
managedLedgerDefaultWriteQuorum=2
managedLedgerDefaultAckQuorum=2

So I should be able to take any one of the 3 machines down for a while without any disruption in service right? And when I bring it up will it get copies of all the message it missed? I just want to make sure I am understanding things correctly before I do this to our live cluster. I don’t want to have a very bad weekend!

frequently because I'm debugging Windows services that use MSMQ,
i need to review the Private Queues ...

I open Computer Management,
expand Services and Applications,
then expand Message Queuing and
Private Queues ... I know it's
only a couple of extra clicks
by it gets tiring because I
really do need to do it quite
often ...

some components can open outside of
Computer Management, e.g.: Event Viewer
via Start, Run, eventvwr.

is it possible to do the same for
Message Queuing?

thnx ~~ gerry (lowry)

There are many open source Message queues for Linux, and I need some help deciding what I should go for.

My problem is simple - I get sent a list of files that needs to be processed. Each job can't be split up, but they are self contained and can be spread to multiple computers.

I'm thinking of solving this using a message queue. Multiple clients send a message to a central queue. Each queue has a number of subscribers that will take jobs from that queue when they have finished processing the current job.

Ideally it should have the following qualities

• Message queue must be able to store unprocessed messages in case of a shutdown/reboot
• A job can only be processed by a single subscriber (don't want duplicate jobs)
• The subscribers should be able to send jobs of their own, that will be processed by a different set of subscribers.

Can anyone suggest a simple to use message queue?

I'm really curious about this. The question (highlighed in bold):

Can someone name ONE GOOD REASON to have their email server permanently set up to auto-fail/immediate-fail on 4xx codes?

Because frankly, it sounds like "their" setups are broken out-of-the-box. SMTP is not Instant Messaging. Stop treating it like IRC or Jabber or MSN or insert-IM-technology-here. I don't know what possesses people to have the "IMMEDIATE DELIVERY OR FAIL" mentality with SMTP setups, but they need to stop doing that. It just plain breaks things. Every two or three years, I stumble into this. Someone, somewhere, has decided in their infinite wisdom that 4xx codes are immediate failures, and suddenly its OMGWTFBBQ THE INTARNETZ ARE BORKEN, HALP SKY IS FALLING instead of "oh, it'll re-attempt delivery in about 30 minutes". It amazes me how it suddenly becomes "my" problem that a message won't go through, because someone else misconfigured "their" SMTP service.

IF there is a legitimate reason for having your server permanently set up in this manner, then the first good answer will get the check.

IF there is no good reason (and I suspect there isn't), then the first good-sounding-if-still-logically-flawed answer will get the check.

Simple question time: where can I define the requeue interval for sendmail? By default SendMail is configured to retry delivery of deferred messages once every hour. I'd like to set that to be more frequent. Is there a DAEMON option somewhere for this?

-M