I using the Java API.
I seem to get these RemoteTransportExceptions:
Caused by: org.elasticsearch.action.UnavailableShardsException:
[registry]  shardIt,  active : Timeout waiting for [1m], request:
It just seems to sit there and every now and then it will proceed but hang
On Mon, Oct 17, 2011 at 5:11 PM, Shay Banon email@example.com wrote:
Which client are you using? Have the different nodes found each other and
formed a cluster (you can see that in the logs, or the cluster state API)?
One of the reasons why it might "hang" (not really hang, but wait for a
timeout fo 1m) is if there aren't enough active shards for hte document to
be indexed. This can happen, for example, if you have 1 node, and set
number_of_replicas to 2 (3 copies), and then try and index a doc. By
default, it expects a quorum of shards to be active. See write consistency
in the index API docs:
On Tue, Oct 18, 2011 at 2:02 AM, Anthony Ikeda <
Thanks Shay. Also as for the ports, I set up a basic cluster in our dev
environment, as far as I know there are no blocked ports, but trying to
index any data leaves the Client hanging - no errors are reported thus the
question about what ports need to be opened.
Running locally works fine though.
On Mon, Oct 17, 2011 at 4:55 PM, Shay Banon firstname.lastname@example.org wrote:
On Mon, Oct 17, 2011 at 11:21 PM, Anthony Ikeda <
We are looking at using elastic search to index our data that we
currently store to Cassandra. I was wondering if there are any
concerns running elastic search on the same nodes that we use for
Running them on the same machine is possible, but, they will affect each
other (IO, network, CPU).
Also which ports are required to be opened for proper communication
from node to node and client to node?
By default, elasticsearch will use post 9300 for node to node and Java
API communication, and port 9200 for HTTP endpoint.