Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

namespace-regex config bug #524

Open
rentiansheng opened this issue Jun 4, 2021 · 2 comments · May be fixed by #525
Open

namespace-regex config bug #524

rentiansheng opened this issue Jun 4, 2021 · 2 comments · May be fixed by #525

Comments

@rentiansheng
Copy link
Contributor

rentiansheng commented Jun 4, 2021 •
edited
Loading

  • (Unauthorized) not authorized on admin to execute command
  • (Unauthorized) not authorized on config to execute command

error detail:

ERROR 2021/06/04 20:37:45 Error starting change stream. Will retry: (Unauthorized) not authorized on admin to execute command { aggregate: 1, pipeline: [ { $changeStream: { allChangesForCluster: true, fullDocument: "updateLookup" } } ], cursor: {}, lsid: { id: UUID("89609306-00c3-429d-b584-58a58da89f5d") }, $clusterTime: { clusterTime: Timestamp(1622810252, 1), signature: { hash: BinData(0, 870E8B4C26D5988646DC3131697CA1E57580750E), keyId: 6940129626588971010 } }, $db: "admin", $readPreference: { mode: "primary" } }
rentiansheng added a commit to rentiansheng/monstache that referenced this issue Jun 4, 2021
@rentiansheng
fix: use namespace-regix config has not authorized bug issue rwynn#524
3820073
@rentiansheng rentiansheng linked a pull request Jun 4, 2021 that will close this issue
Open
@patrickserrano
Copy link

@rwynn I'm seeing this too, and rough timeline on when we could see #525 merged and released? thanks!

@rwynn
Copy link
Owner

rwynn commented Aug 16, 2021

Hey @patrickserrano I'm not so sure about the direction the pull request takes. When that is applied monstache will no longer create a change stream at the deployment level. That has been the default for a long time since it means that a change to any MongoDB collection gets propogated to Elasticsearch.

The namespace-regex-config was not about selecting the collections to sync but rather to simply be a client side filter. The actually configuration for what to watch was always supposed to come from the change-stream-namespaces config which lets you select at the deployment, database, or collection level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: use namespace-regex config has not authorized bug rentiansheng/monstache
3 participants
@rwynn @patrickserrano @rentiansheng