Hi All,
My client has a cosmos db mirror that had been working well for several weeks. A lease container was added to support a CosmoDBTrigger via a functions app. The mirror stopped adding new data after this container was added. The lease container is being mirrored successfully however. The mirror monitor page showed "Running" with no warnings on either container, and the container can be quieried in the source database selection in the database mirror (it does return new data). The mirror was recreated and now the monitoring shows "Running with warnings" and success on the lease container. Documentation indicates that the change data feed / lease container does not interfere with the continuous backup process serving the mirror, however this appears to be quite the coincidence that the mirror stopped the moment the lease container was created. Any suggestions, help, or previous experience encountering this would be helpful. Thank you!
