Hello,
I observe a very strange behaviour with concurrent tailable consumers and
persistent tail tracking. Perhaps you have an idea:
Scenario:
- A MongoDB Replicaset of 3 servers, running MongoDB 2.4.11
- 2 camel servers (tomcat7 with Sun JDK, Camel 2.13.1)
- On each server, 5 tailable cursor consumer endpoints, listening on 5
different collections with persistent tail tracking enabled
- The persistent id for each consumer endpoint is defined as:
"<hostname>_<CollectionName>"
- So the collection storing the persistent tail tracking information
("consumedUpdates") looks something like this:
The endpoint configuration looks something like this:
mongodb://mongoDBInstance?collection=<COLLECTION>&database=...&persistentId=<HOST>_<COLLECTION>&persistentTailTracking=true&tailTrackCollection=consumedUpdates&tailTrackIncreasingField=updateId
The problem: Only one document in the "consumedUpdates" collection seems to
be updated, no matter which collection or host is affected. It seems like
this is always the first document in the collection. So all consumers write
into the same document, overwriting information coming from other consumers
:(
The problem does not occur on our test environment (1 camel server, 1
MongoDB, both on the same machine).
Any ideas?
Thanks for your help!
Best regards,
Joerg
--
View this message in context:
http://camel.465427.n5.nabble.com/MongoDB-Persistent-tail-tracking-with-concurrent-tailable-consumers-tp5759131.html
Sent from the Camel - Users mailing list archive at Nabble.com.
