Bulk indexing tips for Elastic search and Cassandra River


(utkarsh2012) #1

Hello,

I have been working on a cassandra river which triggers periodically and
indexes all data in a cassandra column family. The implementation for now
spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in 10mins.
But after a 1hour, the indexing became very slow and it indexed around 8M
documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed
was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to
improve bulk indexing. I am running 1 node with 5 shared with 2GB of
ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here:
https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU
in 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable
performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

--
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.


(Jörg Prante) #2

You need to throttle bulk indexing, for example with
org.elasticsearch.action.bulk.BulkProcessor, in order to get stable feed
rate over long periods of time.

Check out JDBC river for an example:
https://github.com/jprante/elasticsearch-river-jdbc/blob/master/src/main/java/org/elasticsearch/river/jdbc/strategy/simple/SimpleRiverMouth.java

What is your document size? It is also valuable to measure bulk indexing
throughput in MB/sec. I can index up to 8 MB/sec on an average desktop
PC in a single node cluster (which is ~10-15.000 docs per sec for my doc
size).

Note, indexing speed can greatly be improved by fixing the slowest part
of the system first: the I/O subsystem. Fast disk arrays (RAID 0) or
even SSD devices help a lot.

Jörg

Am 29.03.13 22:01, schrieb utkarsh2012@gmail.com:

Hello,

I have been working on a cassandra river which triggers periodically
and indexes all data in a cassandra column family. The implementation
for now spawns 10 threads and processes 10k documents (with 13
columns)/thread.
The performance initially was very good. It indexed 1M documents in
10mins. But after a 1hour, the indexing became very slow and it
indexed around 8M documents. I am trying to index a total of 50M
documents.

I have attached a screenshot of the memory and CPU usage. What I
noticed was, a lot of merge threads spawned up which reduced the speed
considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak
to improve bulk indexing. I am running 1 node with 5 shared with 2GB
of ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here:
https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU
in 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves
acceptable performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

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.


(ashwini) #3

I am new to elasticsearch and trying to learn how to integrate elasticsearch with cassandra.
Can you give me some pointers.

Thanks,
Ashwini


(ashwini) #4

Hello,

I am new to elasticsearch. I am trying
use https://github.com/eBay/cassandra-river plugin to store data to
cassandra.
I dont see the data in cassandra. My search queries are returning from the
elasticsearch.

Please advise.

Thanks,
Ashwini

On Friday, March 29, 2013 2:01:14 PM UTC-7, utkar...@gmail.com wrote:

Hello,

I have been working on a cassandra river which triggers periodically and
indexes all data in a cassandra column family. The implementation for now
spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in
10mins. But after a 1hour, the indexing became very slow and it indexed
around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed
was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to
improve bulk indexing. I am running 1 node with 5 shared with 2GB of
ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here:
https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeUin 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable
performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

--
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.


(utkarsh2012) #5

Hi Ashwini,

A river works the other way around, it moves data from cassandra to
elasticsearch so that you can index it.
I wrote cassandra-river as a proof of concept and hacked up in few days.
Please feel free to file a bug or send a pull request.

Thanks,
-Utkarsh

On Tue, Nov 19, 2013 at 2:41 PM, Ashwini Lohit ashwini.2284@gmail.comwrote:

Hello,

I am new to elasticsearch. I am trying use
https://github.com/eBay/cassandra-river plugin to store data to
cassandra.
I dont see the data in cassandra. My search queries are returning from the
elasticsearch.

Please advise.

Thanks,
Ashwini

On Friday, March 29, 2013 2:01:14 PM UTC-7, utkar...@gmail.com wrote:

Hello,

I have been working on a cassandra river which triggers periodically and
indexes all data in a cassandra column family. The implementation for now
spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in
10mins. But after a 1hour, the indexing became very slow and it indexed
around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed
was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to
improve bulk indexing. I am running 1 node with 5 shared with 2GB of
ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here: https://groups.google.com/
forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU in 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable
performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/M1aJqvAIpZE/unsubscribe.

To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks,
-Utkarsh

--
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.


(David Pilato) #6

I think this river index docs from cassandra to Elasticsearch.
Not the opposite.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 nov. 2013 à 23:41, Ashwini Lohit ashwini.2284@gmail.com a écrit :

Hello,

I am new to elasticsearch. I am trying use https://github.com/eBay/cassandra-river plugin to store data to cassandra.
I dont see the data in cassandra. My search queries are returning from the elasticsearch.

Please advise.

Thanks,
Ashwini

On Friday, March 29, 2013 2:01:14 PM UTC-7, utkar...@gmail.com wrote:
Hello,

I have been working on a cassandra river which triggers periodically and indexes all data in a cassandra column family. The implementation for now spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in 10mins. But after a 1hour, the indexing became very slow and it indexed around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]" daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to improve bulk indexing. I am running 1 node with 5 shared with 2GB of ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here: https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU in 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable performance.

Thanks,
-Utkarsh

--
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.


(ashwini) #7

On Friday, March 29, 2013 2:01:14 PM UTC-7, utkar...@gmail.com wrote:

Hello,

I have been working on a cassandra river which triggers periodically and
indexes all data in a cassandra column family. The implementation for now
spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in
10mins. But after a 1hour, the indexing became very slow and it indexed
around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed
was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to
improve bulk indexing. I am running 1 node with 5 shared with 2GB of
ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here:
https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeUin 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable
performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

--
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.


(David Pilato) #8

Moving this to the ML.

Did you restart the node?
What are the 15 first lines of your node logs?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 22 nov. 2013 à 21:41, Ashwini Lohit ashwini.2284@gmail.com a écrit :

Logs:

[2013-11-22 19:33:48,991][DEBUG][river.cluster ] [Gigantus] processing [reroute_rivers_node_changed]: no change in cluster_state
[2013-11-22 19:33:49,993][DEBUG][river.cluster ] [Gigantus] processing [reroute_rivers_node_changed]: execute
[2013-11-22 19:33:50,014][INFO ][river.routing ] [Gigantus] no river _meta document found, retrying in 1000 ms
[2013-11-22 19:33:50,014][DEBUG][river.cluster ] [Gigantus] processing [reroute_rivers_node_changed]: no change in cluster_state
[2013-11-22 19:33:51,017][DEBUG][river.cluster ] [Gigantus] processing [reroute_rivers_node_changed]: execute
[2013-11-22 19:33:51,018][WARN ][river.routing ] [Gigantus] no river _meta document found after 5 attempts
[2013-11-22 19:33:51,018][DEBUG][river.cluster ] [Gigantus] processing [reroute_rivers_node_changed]: no change in cluster_state
[2013-11-22 19:35:09,915][DEBUG][cluster.service ] [Gigantus] processing [update-mapping [_river][test]]: execute
[2013-11-22 19:35:09,916][DEBUG][cluster.metadata ] [Gigantus] [_river] update_mapping [test] ignoring mapping update task as it's source is equal to ours
[2013-11-22 19:35:09,917][DEBUG][cluster.service ] [Gigantus] processing [update-mapping [_river][test]]: no change in cluster_state

This is all the info I see in the logs. Looks like the river is loaded.

Thanks,
Ashwini

On Fri, Nov 22, 2013 at 12:32 PM, David Pilato david@pilato.fr wrote:

Anything in logs?
Is the river loaded?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 22 nov. 2013 à 20:21, Ashwini Lohit ashwini.2284@gmail.com a écrit :

Hello,

Thanks for the reply. I might have some misconfiguration in the settings.

Version:
Elasticsearch : 0.90.5
Cassandra: 1.1.6
Cassandra River - https://github.com/eBay/cassandra-river (latest)

I did the following steps

  1. Created an instance of cassandra
  2. Created keyspace test
  3. Created column_family
  4. Populated 10 records
    like this
    [default@test] SET users['bobbyjo']['full_name']='Robert Jones';

[default@test] SET users['bobbyjo']['email']='bobjones@gmail.com';

[default@test] SET users['bobbyjo']['state']='TX';

[default@test] SET users['bobbyjo']['gender']='M';

[default@test] SET users['bobbyjo']['birth_year']='1975';
5. Installed elasticsearch cassandra river plugin
6.curl -XPUT "http://:9200/_river/abc/_meta" -d'
{
"type" : "cassandra",
"cassandra" : {
"cluster_name" : "demo",
"keyspace" : "test",
"column_family" : "users",
"hosts" : ":9160"
},
"index" : {
"index" : "abc",
"type" : "cassandra"
}
}'

I still dont see the data being indexed in elastic search, here is what I ran to look at it.
curl -XGET "http://:9200/abc/cassandra/_search" -d'
{
"query": {
"match_all": {

    }
}

}'
I also tried

curl -XGET "http://:9200/users/_search" -d'
{
"query": {
"match_all": {

    }
}

}'

Please advise.

Thanks,
Ashwini
On Tuesday, November 19, 2013 3:33:00 PM UTC-8, David Pilato wrote:

I think this river index docs from cassandra to Elasticsearch.
Not the opposite.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 nov. 2013 à 23:41, Ashwini Lohit ashwin...@gmail.com a écrit :

Hello,

I am new to elasticsearch. I am trying use https://github.com/eBay/cassandra-river plugin to store data to cassandra.
I dont see the data in cassandra. My search queries are returning from the elasticsearch.

Please advise.

Thanks,
Ashwini

On Friday, March 29, 2013 2:01:14 PM UTC-7, utkar...@gmail.com wrote:

Hello,

I have been working on a cassandra river which triggers periodically and indexes all data in a cassandra column family. The implementation for now spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in 10mins. But after a 1hour, the indexing became very slow and it indexed around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]" daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to improve bulk indexing. I am running 1 node with 5 shared with 2GB of ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here: https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU in 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable performance.

Thanks,
-Utkarsh

--
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 elasticsearc...@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.


(AKhan) #9

cassandra-river is not working in my case too and I am getting exceptions
on server side.

elasticsearch.common.UUID;

On Friday, March 29, 2013 10:01:14 PM UTC+1, utkar...@gmail.com wrote:

Hello,

I have been working on a cassandra river which triggers periodically and
indexes all data in a cassandra column family. The implementation for now
spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in
10mins. But after a 1hour, the indexing became very slow and it indexed
around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed
was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to
improve bulk indexing. I am running 1 node with 5 shared with 2GB of
ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here:
https://groups.google.com/forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeUin 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable
performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1f5550ca-d53e-4513-b691-8992e0504533%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(utkarsh2012) #10

Can you please file a bug (https://github.com/eBay/cassandra-river/issues)
or share the stacktrace?

Thanks,
-Utkarsh

On Tue, Feb 4, 2014 at 8:54 AM, AKhan ansark6@gmail.com wrote:

cassandra-river is not working in my case too and I am getting exceptions
on server side.

elasticsearch.common.UUID;

On Friday, March 29, 2013 10:01:14 PM UTC+1, utkar...@gmail.com wrote:

Hello,

I have been working on a cassandra river which triggers periodically and
indexes all data in a cassandra column family. The implementation for now
spawns 10 threads and processes 10k documents (with 13 columns)/thread.
The performance initially was very good. It indexed 1M documents in
10mins. But after a 1hour, the indexing became very slow and it indexed
around 8M documents. I am trying to index a total of 50M documents.

I have attached a screenshot of the memory and CPU usage. What I noticed
was, a lot of merge threads spawned up which reduced the speed considerably:
"elasticsearch[Doppelganger][[prodinfo][1]: Lucene Merge Thread #329]"
daemon prio=10 tid=0x2a630000 nid=0x4c28 runnable [0x246bd000]

So, I believe this has to do with some configuration which I can tweak to
improve bulk indexing. I am running 1 node with 5 shared with 2GB of
ES_HEAP_SIZE and no replicas for now.

Shay mentioned some tips here: https://groups.google.com/
forum/?fromgroups=#!topic/elasticsearch/APWxRLrMOeU in 2011.
Wanted to know if there are any bulk indexing performance improvements?

I am also using: bulk.execute().addListener() (async) in place of
bulk.execute().actionGet() (sync)

I am planning to share the cassandra-river as soon its achieves acceptable
performance.

https://lh5.googleusercontent.com/-G8kxNXFaUmc/UVYAPHN-NFI/AAAAAAAAAgw/rmcLu6P1Urg/s1600/bigdesk_ES.png

https://lh3.googleusercontent.com/-8RokQMwPSW0/UVYAJFwUvrI/AAAAAAAAAgo/GTEdX5MkTwA/s1600/visualvm_Es.png

Thanks,
-Utkarsh

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/M1aJqvAIpZE/unsubscribe.

To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/1f5550ca-d53e-4513-b691-8992e0504533%40googlegroups.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
Thanks,
-Utkarsh

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CADjjot9uWLyBw%3D7ESYL%3D-sHLJmBLigPx4iON1UjsXNgpWsm18g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #11