elasticsearch thoughts; also, a bug.

Hey all.  I just wanted to share my experiences with elasticsearch on
a 10 node cluster and my thoughts.  I've had a lot of fun using it,
and will make heavy use of it in the future, :)

http://blog.jinked.com/posts/30

I wanted to take the time to address two things really quickly
though.  To answer Shay's question, the trivial lacking areas in
elasticsearch where Solr has functionality that elasticsearch doesn't,
are things such as the contrib/data import handler. We actually do use
it in one case, but only because of a limitation in Solr that doesn't
exist in elasticsearch (NRT, to be exact).  Moving over to
elasticsearch from Solr would eliminate our need for the data import
handler, as we can distribute/index this particular dataset in real
time.

The second thing I wanted to bring up was a bug.  I've seen this
happen before with certain software (including software I've written
my self), so it's not too uncommon.  elasticsearch will listen on
0.0.0.0 by default, but if the machine has two IP addresses, it will
actually listen on one IP address and send requests/multicast out on
the other.  The result is elasticsearch will not become a member of
the cluster and will isolate it self on an island on that one
machine.  Of course, one work around is to define the IP to bind to in
the config, but it'd certainly go a long way in ease of use if we can
just setup elasticsearch and go. In particular since we share a single
config file on a cluster file system.

Flippin' amazing software though.  elasticsearch's cluster model is
how all multi-node software should function.

Cheers!
-Antonio