[SERVER-14760] Mongo Connector Failing Unexpectedly Created: 01/Aug/14  Updated: 05/Aug/14  Resolved: 05/Aug/14

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: karan agarwal Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I am using mongo-connector (Latest repo- https://github.com/10gen-labs/mongo-connector.git) to index data in ElasticSearch (1.1.1).
I am indexing ~50000 new documents daily.

Mongo-connector fails unexpectedly with logs-
1. ERROR - OplogManager: Last entry no longer in oplog cannot recover! .
This usually happens when the indexing becomes slow and the delta between oplog and elasticsearch becomes ~> 5000 documents.

2. WARNING - DELETE /####index_name/string/53d870d76e2f9017db0b6bda?refresh=true [status:404 request:0.004s]
INFO - > None

ReplicaSet info-
SECONDARY> rs.printReplicationInfo()
configured oplog size: 3751.087890625MB
log length start to end: 39595secs (11hrs)
oplog first event time: Fri Aug 01 2014 01:24:12 GMT+0530 (IST)
oplog last event time: Fri Aug 01 2014 12:24:07 GMT+0530 (IST)
now: Fri Aug 01 2014 12:24:07 GMT+0530 (IST)

I am starting mongo-connector with below parameters-
mongo-connector -m localhost:27017 -t es-ip:9200 --continue-on-error --auto-commit-interval=0 -d doc_managers/elastic_doc_manager.py -n index_foo -i name,age.....,ph --batch-size=1000 --continue-on-error -o foo-config.txt -w /log/foo.log &



 Comments   
Comment by Thomas Rueckstiess [ 05/Aug/14 ]

Hi Karan,

The SERVER project is for reporting bugs and feature requests against the core MongoDB server. I've moved your question to the github issues page of mongo connector, see this issue.

Regards,
Thomas

Generated at Thu Feb 08 03:35:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.