I'm trying to run a river query which fetches 10000 records scheduled at 1
minute interval. The first time it runs, metrics is 10000 rows and after a
gap of 1 minute that is (scheduled interval) metrics is 20000 rows. What
does this mean? Although the number of hits i get on querying the river
index is 10000 itself. Why do the metrics on rows keep on increasing by a
factor of 10000 each time?
These are diagnostic messages which have been crept into one of the
releases. Latest version has metrics logging disabled, it must be enabled
by settings.
The metrics count the number of rows fetched form the database, and prints
them at every minute. This is not the number of documents in ES.
The metrics print an average mean of the row count, so you can see that
your database sent 250 rows per second. It also counts the data volume in
bytes, and print the measure of megabytes per second, which is in
interesting number for throughput.
I'm trying to run a river query which fetches 10000 records scheduled at 1
minute interval. The first time it runs, metrics is 10000 rows and after a
gap of 1 minute that is (scheduled interval) metrics is 20000 rows. What
does this mean? Although the number of hits i get on querying the river
index is 10000 itself. Why do the metrics on rows keep on increasing by a
factor of 10000 each time?
On Friday, January 16, 2015 at 6:08:49 PM UTC+5:30, Jörg Prante wrote:
These are diagnostic messages which have been crept into one of the
releases. Latest version has metrics logging disabled, it must be enabled
by settings.
The metrics count the number of rows fetched form the database, and prints
them at every minute. This is not the number of documents in ES.
The metrics print an average mean of the row count, so you can see that
your database sent 250 rows per second. It also counts the data volume in
bytes, and print the measure of megabytes per second, which is in
interesting number for throughput.
I'm trying to run a river query which fetches 10000 records scheduled at
1 minute interval. The first time it runs, metrics is 10000 rows and after
a gap of 1 minute that is (scheduled interval) metrics is 20000 rows. What
does this mean? Although the number of hits i get on querying the river
index is 10000 itself. Why do the metrics on rows keep on increasing by a
factor of 10000 each time?
So here,
Average no of rows picked per second is 170 and what do the values in the
brackets mean (147.82076731011736 30.98274869393544 10.409690875802436).
and also ingest metrics: elapsed 8 seconds mean that the total time taken
in the corresponding poll is 8 seconds?
So here,
Average no of rows picked per second is 170 and what do the values in the
brackets mean (147.82076731011736 30.98274869393544 10.409690875802436).
and also ingest metrics: elapsed 8 seconds mean that the total time taken
in the corresponding poll is 8 seconds?
Okay. Thanks a lot. Is there any other way in which I can see the metrics.
If I have indexed my db with 20000 records in Elasticsearch, for that I can
see the metrics as above. But say that, I have made one new
insert/update/delete into my db and that is picked by elasticsearch, is
there any way in which I can see the time taken for that one particular
insert/update/delete?
On Monday, January 19, 2015 at 3:36:47 PM UTC+5:30, Jörg Prante wrote:
The numbers in brackets mean the average numbers over the last 1 / 5 / 15
minutes. This useful for a long running indexer.
The "elapsed" time is the time since this metric counter is active.
So here,
Average no of rows picked per second is 170 and what do the values in
the brackets mean (147.82076731011736 30.98274869393544
10.409690875802436).
and also ingest metrics: elapsed 8 seconds mean that the total time taken
in the corresponding poll is 8 seconds?
As said, insert/update/delete in DB are not visible to the JDBC plugin and
they can not be detected by the JDBC plugin. The metric is for the SQL
select statement the plugin is using. If you mean insert/update/delete in
ES, there is no such thing, there are indexing operations performed in
bulk, which can be monitored by ES monitoring plugins or ES metrics.
Okay. Thanks a lot. Is there any other way in which I can see the metrics.
If I have indexed my db with 20000 records in Elasticsearch, for that I can
see the metrics as above. But say that, I have made one new
insert/update/delete into my db and that is picked by elasticsearch, is
there any way in which I can see the time taken for that one particular
insert/update/delete?
On Monday, January 19, 2015 at 3:36:47 PM UTC+5:30, Jörg Prante wrote:
The numbers in brackets mean the average numbers over the last 1 / 5 / 15
minutes. This useful for a long running indexer.
The "elapsed" time is the time since this metric counter is active.
So here,
Average no of rows picked per second is 170 and what do the values in
the brackets mean (147.82076731011736 30.98274869393544
10.409690875802436).
and also ingest metrics: elapsed 8 seconds mean that the total time
taken in the corresponding poll is 8 seconds?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
!