# Elasticsearch mongodb river issues
**URL:** https://discuss.elastic.co/t/elasticsearch-mongodb-river-issues/12875
**Category:** Elasticsearch
**Created:** [July 21, 2013, 3:02pm UTC](https://discuss.elastic.co/t/elasticsearch-mongodb-river-issues/12875 "2013-07-21T15:02:23Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Aditya\_Arisetty](https://discuss.elastic.co/u/Aditya_Arisetty)
#### Post date: [July 21, 2013, 3:02pm UTC](https://discuss.elastic.co/t/elasticsearch-mongodb-river-issues/12875/1 "2013-07-21T15:02:23Z")
Hi,
I have a mongodb with 2 collections lets say they are "A" and "B".
I am using elasticsearch to index both the above collections with the help
of "[https://github.com/richardwilly98/elasticsearch-river-mongodb/](https://github.com/richardwilly98/elasticsearch-river-mongodb/)" mongodb
river.
Collection "A" has 5million documents and Collection "B" has 10 million
documents.
The problems I am facing are as follows.
1. Indexing is taking a long time.
2. The river keeps on querying the oplog even when there is no operation
performed. For eg: I see oplog queries on mongodb on 21 July even when no
operation is performed on that day.
Is this a issue with mongodb tailable or is it the way I configured my
elasticsearch river?
Any help with this please.
Thanks,
Aditya A
--
Brand View\* \*- Analyse the retail market, instantly
UK: 0844 357 9970
USA: 1-800-968-1876
Latest from the blog: New Out of Stock feature now available -
[www.brandview.com/blog](http://www.brandview.com/blog)
--
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](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:25am UTC](https://discuss.elastic.co/t/elasticsearch-mongodb-river-issues/12875/2 "2017-07-06T02:25:21Z")