ElasticSearch upgrade

Hi All,

I am using ElasticSearch-0.90.0.RC2 in distributed mode.

Now i want to upgrade ElasticSearch version to recent stable release-*0.90.2
*.

My main purpose is to upgrade ElasticSearch without shutting down whole
cluster.

I want to know if on one machine i upgrade ElasticSearch and add that node
to same running cluster while on another machines old ElasticSearch version
are running. Will it create any problem?

If i upgrade whole cluster to new ElasticSearch version then will it be
consistent with previous indexed data ? If not then how we can recover and
use that data ?

Thanks in Advance !

Regards,
Hanish

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

elasticsearch should be combatible between minor versions, so you should be
able to do rolling upgrades from 0.90.0RC2 to 0.90.2. However, I have had
issues in the past between minor versions (0.19.2 and 0.19.8), but normally
that is not the case. I recently upgraded from 0.90.1 to 0.90.2 with no
issues.

As far as the data/index goes, your data will be available/consistent since
the underlying Lucene internals can deal with the index. Hopefully you can
perform a rolling upgrade with no indexing taking place. Flush the
transaction logs before so that the nodes can come back up cleanly.

--
Ivan

On Thu, Jul 4, 2013 at 7:27 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:

Hi All,

I am using ElasticSearch-0.90.0.RC2 in distributed mode.

Now i want to upgrade ElasticSearch version to recent stable release-*
0.90.2*.

My main purpose is to upgrade ElasticSearch without shutting down whole
cluster.

I want to know if on one machine i upgrade ElasticSearch and add that node
to same running cluster while on another machines old ElasticSearch version
are running. Will it create any problem?

If i upgrade whole cluster to new ElasticSearch version then will it be
consistent with previous indexed data ? If not then how we can recover and
use that data ?

Thanks in Advance !

Regards,
Hanish

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi

I am trying to do rolling upgrades from 0.90.0RC2 to 0.90.2 but getting
below exception:

[hanish@impadmin elasticsearch]$ bin/elasticsearch -f
[2013-07-05 18:54:51,322][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: initializing ...
[2013-07-05 18:54:51,326][INFO ][plugins ] [Black Knight]
loaded [], sites [browser]
[2013-07-05 18:54:52,842][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: initialized
[2013-07-05 18:54:52,842][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: starting ...
[2013-07-05 18:54:52,895][INFO ][transport ] [Black Knight]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
172.26.32.84:9300]}
[2013-07-05 18:54:55,915][INFO ][cluster.service ] [Black Knight]
new_master [Black
Knight][uWSasGtnQqe4azl40JOE3w][inet[/172.26.32.84:9300]]{master=true},
reason: zen-disco-join (elected_as_master)
[2013-07-05 18:54:55,937][INFO ][discovery ] [Black Knight]
elasticsearchhanish/uWSasGtnQqe4azl40JOE3w
[2013-07-05 18:54:55,961][INFO ][http ] [Black Knight]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
172.26.32.84:9200]}
[2013-07-05 18:54:55,961][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: started
[2013-07-05 18:54:56,237][WARN ][indices.cluster ] [Black Knight]
[mlivemass_ipdr_475287][2] failed to create shard
org.elasticsearch.index.shard.IndexShardCreationException:
[mlivemass_ipdr_475287][2] failed to create shard
at
org.elasticsearch.index.service.InternalIndexService.createShard(InternalIndexService.java:342)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.applyInitializingShard(IndicesClusterStateService.java:567)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.applyNewOrUpdatedShards(IndicesClusterStateService.java:532)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.clusterChanged(IndicesClusterStateService.java:174)
at
org.elasticsearch.cluster.service.InternalClusterService$2.run(InternalClusterService.java:321)
at
org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:95)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.elasticsearch.index.deletionpolicy.DeletionPolicyModule.configure(DeletionPolicyModule.java:46)
at
org.elasticsearch.common.inject.AbstractModule.configure(AbstractModule.java:60)
at
org.elasticsearch.common.inject.spi.Elements$RecordingBinder.install(Elements.java:201)
at
org.elasticsearch.common.inject.spi.Elements.getElements(Elements.java:82)
at
org.elasticsearch.common.inject.InjectorShell$Builder.build(InjectorShell.java:130)
at
org.elasticsearch.common.inject.InjectorBuilder.build(InjectorBuilder.java:99)
at
org.elasticsearch.common.inject.InjectorImpl.createChildInjector(InjectorImpl.java:129)
at
org.elasticsearch.common.inject.ModulesBuilder.createChildInjector(ModulesBuilder.java:66)
at
org.elasticsearch.index.service.InternalIndexService.createShard(InternalIndexService.java:338)
... 8 more

On Thu, Jul 4, 2013 at 4:25 PM, Ivan Brusic ivan@brusic.com wrote:

elasticsearch should be combatible between minor versions, so you should
be able to do rolling upgrades from 0.90.0RC2 to 0.90.2. However, I have
had issues in the past between minor versions (0.19.2 and 0.19.8), but
normally that is not the case. I recently upgraded from 0.90.1 to 0.90.2
with no issues.

As far as the data/index goes, your data will be available/consistent
since the underlying Lucene internals can deal with the index. Hopefully
you can perform a rolling upgrade with no indexing taking place. Flush the
transaction logs before so that the nodes can come back up cleanly.

--
Ivan

On Thu, Jul 4, 2013 at 7:27 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:

Hi All,

I am using ElasticSearch-0.90.0.RC2 in distributed mode.

Now i want to upgrade ElasticSearch version to recent stable release-*
0.90.2*.

My main purpose is to upgrade ElasticSearch without shutting down whole
cluster.

I want to know if on one machine i upgrade ElasticSearch and add that
node to same running cluster while on another machines old ElasticSearch
version are running. Will it create any problem?

If i upgrade whole cluster to new ElasticSearch version then will it be
consistent with previous indexed data ? If not then how we can recover and
use that data ?

Thanks in Advance !

Regards,
Hanish

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks & Regards
Hanish Bansal

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Do you have any Lucene jars in your classpath on the client side? 0.90.2
uses Lucene 4.3.1 and RC2 uses Lucene 4.2.1.

If not, I think it should be raised as an issue on Github.

On Fri, Jul 5, 2013 at 6:27 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:

Hi

I am trying to do rolling upgrades from 0.90.0RC2 to 0.90.2 but getting
below exception:

[hanish@impadmin elasticsearch]$ bin/elasticsearch -f
[2013-07-05 18:54:51,322][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: initializing ...
[2013-07-05 18:54:51,326][INFO ][plugins ] [Black Knight]
loaded [], sites [browser]
[2013-07-05 18:54:52,842][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: initialized
[2013-07-05 18:54:52,842][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: starting ...
[2013-07-05 18:54:52,895][INFO ][transport ] [Black Knight]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
172.26.32.84:9300]}
[2013-07-05 18:54:55,915][INFO ][cluster.service ] [Black Knight]
new_master [Black Knight][uWSasGtnQqe4azl40JOE3w][inet[/172.26.32.84:9300]]{master=true},
reason: zen-disco-join (elected_as_master)
[2013-07-05 18:54:55,937][INFO ][discovery ] [Black Knight]
elasticsearchhanish/uWSasGtnQqe4azl40JOE3w
[2013-07-05 18:54:55,961][INFO ][http ] [Black Knight]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
172.26.32.84:9200]}
[2013-07-05 18:54:55,961][INFO ][node ] [Black Knight]
{0.90.0.RC2}[18874]: started
[2013-07-05 18:54:56,237][WARN ][indices.cluster ] [Black Knight]
[mlivemass_ipdr_475287][2] failed to create shard
org.elasticsearch.index.shard.IndexShardCreationException:
[mlivemass_ipdr_475287][2] failed to create shard
at
org.elasticsearch.index.service.InternalIndexService.createShard(InternalIndexService.java:342)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.applyInitializingShard(IndicesClusterStateService.java:567)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.applyNewOrUpdatedShards(IndicesClusterStateService.java:532)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.clusterChanged(IndicesClusterStateService.java:174)
at
org.elasticsearch.cluster.service.InternalClusterService$2.run(InternalClusterService.java:321)
at
org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:95)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.elasticsearch.index.deletionpolicy.DeletionPolicyModule.configure(DeletionPolicyModule.java:46)
at
org.elasticsearch.common.inject.AbstractModule.configure(AbstractModule.java:60)
at
org.elasticsearch.common.inject.spi.Elements$RecordingBinder.install(Elements.java:201)
at
org.elasticsearch.common.inject.spi.Elements.getElements(Elements.java:82)
at
org.elasticsearch.common.inject.InjectorShell$Builder.build(InjectorShell.java:130)
at
org.elasticsearch.common.inject.InjectorBuilder.build(InjectorBuilder.java:99)
at
org.elasticsearch.common.inject.InjectorImpl.createChildInjector(InjectorImpl.java:129)
at
org.elasticsearch.common.inject.ModulesBuilder.createChildInjector(ModulesBuilder.java:66)
at
org.elasticsearch.index.service.InternalIndexService.createShard(InternalIndexService.java:338)
... 8 more

On Thu, Jul 4, 2013 at 4:25 PM, Ivan Brusic ivan@brusic.com wrote:

elasticsearch should be combatible between minor versions, so you should
be able to do rolling upgrades from 0.90.0RC2 to 0.90.2. However, I have
had issues in the past between minor versions (0.19.2 and 0.19.8), but
normally that is not the case. I recently upgraded from 0.90.1 to 0.90.2
with no issues.

As far as the data/index goes, your data will be available/consistent
since the underlying Lucene internals can deal with the index. Hopefully
you can perform a rolling upgrade with no indexing taking place. Flush the
transaction logs before so that the nodes can come back up cleanly.

--
Ivan

On Thu, Jul 4, 2013 at 7:27 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:

Hi All,

I am using ElasticSearch-0.90.0.RC2 in distributed mode.

Now i want to upgrade ElasticSearch version to recent stable release-*
0.90.2*.

My main purpose is to upgrade ElasticSearch without shutting down whole
cluster.

I want to know if on one machine i upgrade ElasticSearch and add that
node to same running cluster while on another machines old ElasticSearch
version are running. Will it create any problem?

If i upgrade whole cluster to new ElasticSearch version then will it be
consistent with previous indexed data ? If not then how we can recover and
use that data ?

Thanks in Advance !

Regards,
Hanish

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks & Regards
Hanish Bansal

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No, I do not have any Lucene jars in my classpath. ElasticSearch is using
its own Lucene jars.

There may not be any issue for rolling upgrade from 0.90.1 to 0.90.2 but i
am not able to do rolling upgrade from 0.90.0RC2 to 0.90.2.

On Fri, Jul 5, 2013 at 10:12 PM, Ivan Brusic ivan@brusic.com wrote:

Do you have any Lucene jars in your classpath on the client side? 0.90.2
uses Lucene 4.3.1 and RC2 uses Lucene 4.2.1.

If not, I think it should be raised as an issue on Github.

On Fri, Jul 5, 2013 at 6:27 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:

Hi

I am trying to do rolling upgrades from 0.90.0RC2 to 0.90.2 but getting
below exception:

[hanish@impadmin elasticsearch]$ bin/elasticsearch -f
[2013-07-05 18:54:51,322][INFO ][node ] [Black
Knight] {0.90.0.RC2}[18874]: initializing ...
[2013-07-05 18:54:51,326][INFO ][plugins ] [Black
Knight] loaded [], sites [browser]
[2013-07-05 18:54:52,842][INFO ][node ] [Black
Knight] {0.90.0.RC2}[18874]: initialized
[2013-07-05 18:54:52,842][INFO ][node ] [Black
Knight] {0.90.0.RC2}[18874]: starting ...
[2013-07-05 18:54:52,895][INFO ][transport ] [Black
Knight] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
172.26.32.84:9300]}
[2013-07-05 18:54:55,915][INFO ][cluster.service ] [Black
Knight] new_master [Black
Knight][uWSasGtnQqe4azl40JOE3w][inet[/172.26.32.84:9300]]{master=true},
reason: zen-disco-join (elected_as_master)
[2013-07-05 18:54:55,937][INFO ][discovery ] [Black
Knight] elasticsearchhanish/uWSasGtnQqe4azl40JOE3w
[2013-07-05 18:54:55,961][INFO ][http ] [Black
Knight] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
172.26.32.84:9200]}
[2013-07-05 18:54:55,961][INFO ][node ] [Black
Knight] {0.90.0.RC2}[18874]: started
[2013-07-05 18:54:56,237][WARN ][indices.cluster ] [Black
Knight] [mlivemass_ipdr_475287][2] failed to create shard
org.elasticsearch.index.shard.IndexShardCreationException:
[mlivemass_ipdr_475287][2] failed to create shard
at
org.elasticsearch.index.service.InternalIndexService.createShard(InternalIndexService.java:342)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.applyInitializingShard(IndicesClusterStateService.java:567)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.applyNewOrUpdatedShards(IndicesClusterStateService.java:532)
at
org.elasticsearch.indices.cluster.IndicesClusterStateService.clusterChanged(IndicesClusterStateService.java:174)
at
org.elasticsearch.cluster.service.InternalClusterService$2.run(InternalClusterService.java:321)
at
org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:95)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.elasticsearch.index.deletionpolicy.DeletionPolicyModule.configure(DeletionPolicyModule.java:46)
at
org.elasticsearch.common.inject.AbstractModule.configure(AbstractModule.java:60)
at
org.elasticsearch.common.inject.spi.Elements$RecordingBinder.install(Elements.java:201)
at
org.elasticsearch.common.inject.spi.Elements.getElements(Elements.java:82)
at
org.elasticsearch.common.inject.InjectorShell$Builder.build(InjectorShell.java:130)
at
org.elasticsearch.common.inject.InjectorBuilder.build(InjectorBuilder.java:99)
at
org.elasticsearch.common.inject.InjectorImpl.createChildInjector(InjectorImpl.java:129)
at
org.elasticsearch.common.inject.ModulesBuilder.createChildInjector(ModulesBuilder.java:66)
at
org.elasticsearch.index.service.InternalIndexService.createShard(InternalIndexService.java:338)
... 8 more

On Thu, Jul 4, 2013 at 4:25 PM, Ivan Brusic ivan@brusic.com wrote:

elasticsearch should be combatible between minor versions, so you should
be able to do rolling upgrades from 0.90.0RC2 to 0.90.2. However, I have
had issues in the past between minor versions (0.19.2 and 0.19.8), but
normally that is not the case. I recently upgraded from 0.90.1 to 0.90.2
with no issues.

As far as the data/index goes, your data will be available/consistent
since the underlying Lucene internals can deal with the index. Hopefully
you can perform a rolling upgrade with no indexing taking place. Flush the
transaction logs before so that the nodes can come back up cleanly.

--
Ivan

On Thu, Jul 4, 2013 at 7:27 AM, Hanish Bansal <
hanish.bansal.agarwal@gmail.com> wrote:

Hi All,

I am using ElasticSearch-0.90.0.RC2 in distributed mode.

Now i want to upgrade ElasticSearch version to recent stable release-*
0.90.2*.

My main purpose is to upgrade ElasticSearch without shutting down whole
cluster.

I want to know if on one machine i upgrade ElasticSearch and add that
node to same running cluster while on another machines old ElasticSearch
version are running. Will it create any problem?

If i upgrade whole cluster to new ElasticSearch version then will it be
consistent with previous indexed data ? If not then how we can recover and
use that data ?

Thanks in Advance !

Regards,
Hanish

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks & Regards
Hanish Bansal

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks & Regards
Hanish Bansal

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.