I have discovered that we have lots of conflicting services_bom/eom in our MODB databases, does anyone know if this is normal beahaviour? I found this useful command that will show all conflicting documents in a database [docs.couchdb.org/en/stable/replicat…ing-conflicted-documents-with-mango], it needs couchdb rather than bigcouch but we've already upgraded to couchdb. I used this to write a

quick script to audit all our MODBs and found that just about every one has conflicts on these 2 documents. When I examine the revisions it seems that different nodes in the zone (we have 3 apps servers) tried to write the same document at the same time, thats wierd I thought, so I took a look at kt_services_rollover.erl and it seems to me that there is no mechanism to prevent all the nodes trying to do the rollup at precisely the

same time [midnight UTC on 1st of every month], any thoughts anyone?

alane: yeah, there are a couple tasks like that

needing more coordination

in 5.x it is shifting to using the Raft stuff to find a "worker" within the cluster of `task` apps

to do a job like that

mc_ are there will be any changes in billing portion (braintree) in v5?

mentax: not that i'm aware of (at least, i haven't seen PRs related to it)

but other teams may have snuck some in :)

2 weeks