Hi Chris, setting the ack default to 1 would mean folks would have to have
a replica setup and configured otherwise starting a server from scratch
from download would mean an error message to the user.   I hear your risk
of not replicating though perhaps such a use case would be solved through
auto discovery or some other feature/contribution for 0.9.

I would be -1 on changing the default right now because new folks coming in
on a build either as new or migrations simply leaving because they got an
error or even running by just git clone ./sbt package and running (less
steps in 0.8).  There are already expectations on 0.8 we should try to keep
things settling too.

Lastly, folks when they run and go live often will have a chef, cfengine,
puppet, etc script for configuration

Perhaps through some more operation documentation, comments and general
communications to the community we can reduce risk.

Joe Stein
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>

On Tue, Mar 5, 2013 at 8:30 AM, Chris Curtin <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB