Skip to content
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

Deleted document from MongoDB, then started Monstache, Monstache did not delete the document from the Elasticsearch index #31

Open
jpgklassen opened this issue Jul 28, 2022 · 3 comments

Comments

@jpgklassen
Copy link

I deleted a document from the MongoDB database, then started Monstache. Monstache did not delete the document from the Elasticsearch index. I deleted more documents with Monstache running, and it deleted those from the Elasticsearch index.

@oliveiracdz
Copy link

The direct-read-namespaces option allows us to copy entire collections when starting Monstache.
But the sync flow is only from MongoDB to ES... In this case, your best option is to drop ES index manually and start Monstache process again.

@oliveiracdz
Copy link

@rwynn, when running direct-read-namespaces via a cron job like in this sample, would be useful to drop all ES documents that were deleted from mongoDB.

Is there an option like this already?

@rwynn
Copy link
Owner

rwynn commented Sep 22, 2022

hi @oliveiracdz. there is not an option like this. My only thought would be to delete the index in the same cron job before kicking off the direct reads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants