-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: use slaveof force when a pika server recovered and delete CentOS github CI workflow config #2789
fix: use slaveof force when a pika server recovered and delete CentOS github CI workflow config #2789
Conversation
WalkthroughThe changes involve improving the replication mechanism by forcefully updating the master server for a slave in Changes
Sequence Diagram(s)Not applicable due to the nature of the changes which are more infrastructural and function renaming rather than introducing new features or control flows. Assessment against linked issues
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- codis/pkg/topom/topom_group.go (1 hunks)
Additional comments not posted (1)
codis/pkg/topom/topom_group.go (1)
394-395
: Ensure proper error handling for the forceful master update.The change involves using the
updateMasterToNewOneForcefully
function to forcefully update the master server. This approach should be verified to ensure it doesn't introduce any unintended side effects, especially in cases where forceful updates might not be ideal.Please verify that forcefully updating the master server won't cause issues in scenarios where the replication state might be inconsistent or in other edge cases.
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- .github/workflows/pika.yml (1 hunks)
Files skipped from review due to trivial changes (1)
- .github/workflows/pika.yml
release 下的centos 打包也给删了吧 |
The centos package under release should also be deleted. |
… github CI workflow config (OpenAtomFoundation#2789) * updateMasterToNewOneForcefully * remove centos CI --------- Co-authored-by: liuyuecai <[email protected]>
fix #2512
Summary by CodeRabbit
Improvements
Chores
build_on_centos
job from the build configuration to streamline the CI/CD workflow.