Hi
I am exploring the options for providing SSL support for inter-node
communication in elasticsearch and I came across the Salyh's plugin:
https://github.com/salyh/elasticsearch-security-plugin.
But in the documentation it is mentioned that 0.90.10 and greater not yet
working .
Can anyone
you said. But if this is the case the what the
use for setting the multicast as false and setting the unicast host list.
Cant any node join the cluster just like that by setting the unicast to any
node in the cluster. how to limit this.
On Thursday, 13 March 2014 19:46:08 UTC+5:30, Hari Prasad
07:11, Hari Prasad iamha...@gmail.com javascript: a
écrit :
Hi
Can you please explain the following
I first started one node with only its ip in unicast host list and
multicast discovery false. The cluster started with one node.
Then I started another node with its unicast host value
Hi
I am having an elasticsearch cluster. I am using the unicast to discover
nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got ignoring
transient setting [discovery.zen.ping.unicast.hosts], not dynamically
node.
You don't have to modify existing settings, although you should do it to
have updated settings in case of restart.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com javascript: a
écrit :
Hi
I am having
Ok Thank you :)
On Thursday, 13 March 2014 19:35:52 UTC+5:30, David Pilato wrote:
yes
--
*David Pilato* | *Technical Advocate* | *Elasticsearch.com*
@dadoonet https://twitter.com/dadoonet |
@elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 13 mars 2014 à 15:00:10, Hari Prasad
Thank you Binh Ly.
But i am correct to say a restore process should also restore missing
shards. Because in a case where if some shards are missing and restore
didn't help?
On Friday, 7 March 2014 20:58:15 UTC+5:30, Binh Ly wrote:
You can restore an index if it doesn't currently exist. If it
Thank you Binh Ly
On Friday, 7 March 2014 19:12:29 UTC+5:30, Binh Ly wrote:
I don't know specifically what changed from 0 to 45 but as the JVM bugs
are fixed from update to update, it is likely that some kind of low-level
object serialization code will change, which is what your error
Hi
I am trying out the elasticsearch 1.0's snapshot and restore feature. My
doubt is when the restore operation is performed will the missing shards,
those available when snapshot was taken, restored?
--
You received this message because you are subscribed to the Google Groups
elasticsearch
Thanks Binh
It seems thats the problem. in one machine the version was 1.7.0 and in
another one the version was 1.7.0_45.
If you don't mind can you please explain the root cause, as in what
differed in the 2 java version
--
You received this message because you are subscribed to the Google
Hi
I am trying out the elasticsearch 1.0's snapshot and restore feature.
My doubt is when the restore operation is performed will the missing
shards, those available when snapshot was taken, restored?
When i tried this the missing shards were not restored. So does the restore
assumes all the
Thank you David for response
So untill this new settings, that you mention, will i have to mount the shared
location on all the nodes?
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails
Thank you David. That cleared a few things
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion
/current/modules-snapshots.html
Without knowing what you are missing it is difficult to provide more
information
Clint
On 5 March 2014 11:01, Hari Prasad iamha...@gmail.com javascript:wrote:
Hi
I am try to know about the new feature snapshot and restore in the
Elasticsearch 1.0. Can
Hi i have installed the new Elasticsearch 1.0. I am trying to setup cluster
with multicast disabled and unicast ip set. i was successfully able to
index data when only one node is started. But when i start the second i am
getting the following error
sending failed shard for [twitter][2],
But the different ES have different clusters. will that still cause this
problem?
On Wednesday, 5 March 2014 17:02:27 UTC+5:30, Clinton Gormley wrote:
It sounds like you have multiple versions of Elasticsearch running with
the same cluster name.
clint
On 5 March 2014 12:29, Hari Prasad
+5:30, Clinton Gormley wrote:
On 5 March 2014 12:47, Hari Prasad iamha...@gmail.com javascript:wrote:
My clusters have different names, also each of their multicast is false.
There is another node somewhere that is interfering. Have a look in the
logs, or the output from:
curl
The java in all the nodes are 1.7
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web
.
On Wednesday, 5 March 2014 20:06:30 UTC+5:30, Hari Prasad wrote:
The java in all the nodes are 1.7
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch
19 matches
Mail list logo
