Hi Eugene,
Thanks for your comments - I'll do my best to explain where I am coming
from, and to address some of the issues you have raised.
Firstly, where I'm coming from: the data I'm holding and searching against
needs to be 100% backed up because it needs to be audited in the future.
For
Reelsen wrote:
Hey,
just to make sure: You are using the same elasticsearch version and the
same jvm version (including the minor/release version) on the server and
client side?
--Alex
On Fri, Jan 3, 2014 at 7:24 PM, davrob2 davir...@gmail.com
javascript:wrote:
Hi,
So, after
2014 16:53:28 UTC, David Pilato wrote:
Did you change some settings? Timeout seems to be very low here.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 14 janv. 2014 à 17:39, davrob2 davir...@gmail.com javascript: a
écrit :
Hi Jorg,
I move to an IP based config
Hi,
I'm having difficulty connecting with the Java client to 1.0.0.Beta2, the
cluster is up and health, monitoring is fine using elasticsearch Head,
elasticsearch HQ etc.
This is the stack trace I am getting:
https://gist.github.com/dav-rob/8304130
thanks,
David.
--
You received this
Hi,
So, after the upgrade I now can't connect using a java client node using:
Node hostNode = NodeBuilder.nodeBuilder()
.loadConfigSettings(false)
.settings(settings)
.node()
.start();
with these client settings:
index.number_of_shards=1,
index.number_of_replicas=1,