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.

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

question: Persistent Subscription Docs vs. Code #176

Open
seanppayne opened this issue May 23, 2024 · 6 comments
Open

question: Persistent Subscription Docs vs. Code #176

seanppayne opened this issue May 23, 2024 · 6 comments

Comments

@seanppayne
Copy link

// PersistentAllSubscriptionOptions options for most of the persistent subscription requests.
type PersistentAllSubscriptionOptions struct {
	...
	// Requires the request to be performed by the leader of the cluster.
	RequiresLeader bool
}

I am just curious, why is there an option for RequiresLeader when the docs state the following:

Persistent subscriptions only run on the Leader node. This means that more pressure will be put on the Leader node, and there is no option to balance the load to a follower like with a Catch-up subscription.

Is there a use case for this option or should I default to setting it to true?

@YoEight
Copy link
Member

YoEight commented Jun 5, 2024

This is a fair question. As the documentation states it, it's not possible to run persistent subscription on anything than the leader node. All write operations and the subscribe don't need that option indeed. We should remove it from the code to avoid confusion.

@seanppayne
Copy link
Author

seanppayne commented Jun 5, 2024 via email

@YoEight
Copy link
Member

YoEight commented Jun 6, 2024

Please have a go if you want. Will be glad to approve your PR!

@seanppayne
Copy link
Author

Cool, I will give it a shot this weekend.

@seanppayne
Copy link
Author

@YoEight Two questions:

  1. I do not have permission to push code to a branch here if I clone the repo. Should I fork instead?
  2. I get the following error in make test. Do I need to adjust some env vars or do I need some credentials to access this image repository?
Failed to get image auth for docker.eventstore.com. Setting empty credentials for the image: docker.eventstore.com/eventstore-utils/testdata:21.10.0-focal. Error is:credentials not found in native keychain

@YoEight
Copy link
Member

YoEight commented Jun 13, 2024

Hey @seanppayne

I do not have permission to push code to a branch here if I clone the repo. Should I fork instead?

Yes, you need to fork the repo first then open a pull request on the branch you used to write your patch

I get the following error in make test. Do I need to adjust some env vars or do I need some credentials to access this image repository?

You shouldn't have to anything more. Could it be you need to run docker while being root on your machine? I personally always run my docker containers rootless. In any case, don't stress over it, just write your patch, the CI will take care of the testing part.

Thanks for your contribution!

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

No branches or pull requests

2 participants