Skip to content

Conversation

@sampaiodiego
Copy link
Member

Proposed changes (including videos or screenshots)

With the introduction of micro services and the new DB watchers in #19000 the env var DISABLE_PRESENCE_MONITOR used to control whether an instance should be watching for user presence events was not being respected.

Issue(s)

Steps to test or reproduce

Further comments

@sampaiodiego sampaiodiego added this to the 3.14.5 milestone Jun 6, 2021
@sampaiodiego sampaiodiego requested a review from ggazzo June 6, 2021 17:31
@sampaiodiego sampaiodiego merged commit 8a1eb6e into develop Jun 6, 2021
@sampaiodiego sampaiodiego deleted the fix-do-not-watch-user-sessions branch June 6, 2021 21:47
@sampaiodiego sampaiodiego mentioned this pull request Jun 7, 2021
@ankar84
Copy link

ankar84 commented Jun 7, 2021

Am I get this right that using native oplog and DISABLE_PRESENCE_MONITOR honored and works fine. But if we use modern change streams that DISABLE_PRESENCE_MONITOR env not honored and all instances write to db presence changes?

@sampaiodiego
Copy link
Member Author

hey @ankar84 this actually affects native oplog too.. I'll be probably releasing this in a patch for 3.15.x as well.

@ankar84
Copy link

ankar84 commented Jun 7, 2021

hey @ankar84 this actually affects native oplog too.. I'll be probably releasing this in a patch for 3.15.x as well.

This is a really good news, Diego!
And thanks for your great work!

@emikolajczak
Copy link

Sounds fantastic!

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

Successfully merging this pull request may close these issues.

5 participants