-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data reimported on _river index recreation when Mongo collection is empty #251
Comments
If you want to delete all data just drop the collection / database in MongoDB and delete the river and the index in ES then recreate the index. |
I have tried that it when I recreate the index, the data reappears in ES. I'm assuming it's reimporting the data from the oplog but I'm not sure why. Currently running: MongoDB 2.4.3 Do I need to downgrade my ES instead and River plugin to match the version of MongoDB? |
I think you should use the latest version of this plugin, i.e 2.0.0 |
The initial import (using the collection data and not oplog.rs) has been implemented since 1.7.1 [1]. Before 1.7.1 the initial import was using oplog.rs. [1] -#47 |
Sounds like this has been addressed in newer versions of the river |
What's the proper way to delete all data from Mongo and have that reflected in ES?
Steps taken:
"options": {
"secondary_read_preference": true,
"import_all_collections": true,
"skip_initial_import": true
After step #6, the data is re-imported to ES but there's no data in Mongo (db.collection.count() returns 0 on both Primary and Secondary nodes of the replica set)
The text was updated successfully, but these errors were encountered: