-
Notifications
You must be signed in to change notification settings - Fork 23
fix(trillian): lower time on master hold parameters #1202
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
Conversation
Reviewer's GuideThis PR updates the Trillian Logsigner deployment setup by injecting two new election-related flags—master_hold_interval and master_hold_jitter—into the pod’s startup arguments to fine-tune leadership hold timing. Class diagram for updated Logsigner deployment argumentsclassDiagram
class EnsureSignerDeployment {
+EnsureSignerDeployment(instance, labels)
}
EnsureSignerDeployment : --election_system=k8s
EnsureSignerDeployment : --lock_namespace=$(NAMESPACE)
EnsureSignerDeployment : --lock_holder_identity=$(POD_NAME)
EnsureSignerDeployment : +--master_hold_interval=300
EnsureSignerDeployment : +--master_hold_jitter=900
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Caution There are some errors in your PipelineRun template.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- minimum interval to hold master set to 5s - maximum interval to hold master set to 15s Signed-off-by: Tomas Turek <tturek@redhat.com>
8dbe455 to
475c0db
Compare
Summary by Sourcery
Enhancements: