Sergio, I understand the JGroups configuration now.
Does this also apply to the TransportClient() method for connecting?
In the API documentation it has the following example:
Client client = new TransportClient()
We cannot get this to work at all. Is there a different port for this
method of connecting? The example uses 9800 here while everything
else uses 9200. I know 9200 works on the server and is accessible
from our development machines but it doesn't work with the
On Apr 6, 10:19 am, Mindgauge mindga...@gmail.com wrote:
that looks promising. I'll go thrown the docs right now.
On Apr 6, 10:17 am, Sergio Bossa sergio.bo...@gmail.com wrote:
On Tue, Apr 6, 2010 at 4:08 PM, Mindgauge mindga...@gmail.com wrote:
Is your server running on the same network?
I just don't see how I can point the API to a specific cluster.
Default configuration uses IP multicast discovery, so you don't need
to set anything special (unless you want to specify the multicast
However, you'll have hard times trying to use multicast discovery on
EC2 (or any other cloud provider), so I suggest you to switch to
seed-based TCP discovery.
Discovery module configuration is explained at:http://www.elasticsearch.com/docs/elasticsearch/modules/discovery/jgr...
Hope that helps.