-
Notifications
You must be signed in to change notification settings - Fork 801
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
Update Master cluster to Primary cluster #4185
Conversation
CHANGELOG.md
Outdated
@@ -11,7 +11,8 @@ You can find a list of previous releases on the [github releases](https://github | |||
- Added GRPC support. Cadence server will accept requests on both TChannel and GRPC. With dynamic config flag `system.enableGRPCOutbound` it will also switch to GRPC communication internally between server components. | |||
|
|||
### Fixed | |||
- Fixed a bug where an error message is always displayed in Cadence UI `persistence max qps reached for list operations` on the workflow list screen (#3958) | |||
- Fixed a bug where an error message is always displayed in Cadence UI `persistence max qps reached for list operations` on the workflow list screen (#3958) |
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.
This was a wrong fix. I just talked to Justin about it. He will make a fix in web using retry.
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.
Should I delete it?
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.
Yes I think so
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.
Yeah. I deleted it
// all clusters can do domain failover | ||
PrimaryClusterName string `yaml:"primaryClusterName"` |
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.
Just a convention that we introduced breaking changes in configuration -- can we have a version being compatible with warning logs? Likely 0.22.0. And then in 0.23.0 we will remove MasterClusterName
completely.
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.
Yes. This versio is backward compatible. Added a logging message.
CHANGELOG.md
Outdated
@@ -11,7 +11,7 @@ You can find a list of previous releases on the [github releases](https://github | |||
- Added GRPC support. Cadence server will accept requests on both TChannel and GRPC. With dynamic config flag `system.enableGRPCOutbound` it will also switch to GRPC communication internally between server components. | |||
|
|||
### Fixed | |||
- Fixed a bug where an error message is always displayed in Cadence UI `persistence max qps reached for list operations` on the workflow list screen (#3958) | |||
- Replace masterClusterName config with primaryClusterName(#4185) |
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.
Is that for release notes for next release? Maybe putting it more clear that users should update their config
… into remove_master_cluster
What changed?
Update Master cluster to Primary cluster
Why?
Update Master cluster to Primary cluster
How did you test it?
server starts
Potential risks
N/A
Release notes
Documentation Changes
N/A