soldotno / elastic-mongo Goto Github PK

Thank you for going through the trouble of making this available for everyone! I'm currently trying to figure out this same question. Your approach of defining each node in docker-compose.yml doesn't feel right to me because this means you can't use docker-compose scale command. Have you considered this?

I have followed your compose and scripts closely. However, when connecting from a java (spring boot app in my case) I discovered that the config setup for the repl set needs to be the hostname of the machine (or the external IP address). for example,
config= {"_id": "mongors", members:[{"_id": 0, "host": "external-hostname::27017", "priority": 2},{"_id": 1, "host": "external-hostname:27018", "priority": 0},{"_id": 2, "host": "external-hostname:27019", "priority": 0}]}

If I dont and instead give it the docker's internal ip address it does not work. I get a connection error (looks like the hearbeat checks against the address specified in the config variable.

I've set up the cluster successfully, the insert and update ops in mongo will be reflected immediately in the next elastic query. But the delete ops in mongo never appears in elastic, i.e. elastic doesn't delete anything.

I also check the transporter's transformer log, which shows the deleted ops from mongo is logged well and ready for elastic to use.

transformer: {"data":{"_id":{"$oid":"5617763fe2b97de59d269ee8"},"content":"haozi.","title":"Breaking news"},"ns":"harvester-test.entries","op":"insert","ts":1444378175}
transformer: {"data":{"_id":{"$oid":"5617763fe2b97de59d269ee8"},"content":"lucas","title":"Breaking news"},"ns":"harvester-test.entries","op":"update","ts":1444378211}
transformer: {"data":{"_id":{"$oid":"5617763fe2b97de59d269ee8"}},"ns":"harvester-test.entries","op":"delete","ts":1444378780}

Why does it happens?