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

Harbor high availability architecture, dual hosts synchronize with each other based on mirror push events. Once one host goes down, synchronization fails and cannot be retried, resulting in inconsistent data #21119

Open
smallemployees opened this issue Oct 31, 2024 · 2 comments

Comments

@smallemployees
Copy link

If you are reporting a problem, please make sure the following information are provided:

Expected behavior and actual behavior:
A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem.
How can I ensure the consistency of my dual master data in this situation
Steps to reproduce the problem:
Please provide the steps to reproduce this problem.
Harbor high availability architecture, dual hosts synchronize with each other based on mirror push events. Once one host goes down, synchronization fails and cannot be retried, resulting in inconsistent data
Versions:
Please specify the versions of following systems.
2.5.5

  • harbor version: [x.x.x]
  • docker engine version: [y.y.y]
  • docker-compose version: [z.z.z]

Additional context:

  • Harbor config files: You can get them by packaging harbor.yml and files in the same directory, including subdirectory.
  • Log files: You can get them by package the /var/log/harbor/ .
@stonezdj
Copy link
Contributor

stonezdj commented Nov 4, 2024

can you please describe your requirement or issue in detail?

@stonezdj
Copy link
Contributor

stonezdj commented Nov 4, 2024

Maybe do a full replication from active Harbor to standby Harbor can recover it.

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