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

Artifact replication survives peer restart #12

Open
kevstigneev opened this issue May 13, 2015 · 0 comments
Open

Artifact replication survives peer restart #12

kevstigneev opened this issue May 13, 2015 · 0 comments

Comments

@kevstigneev
Copy link
Contributor

If either primary Nexus (that gets an artifact upload) or a replica instance is restarted after an artifact is uploaded to the primary instance, the artifact is replicated after the restart.

Expected results:

  • If the primary Nexus instance is restarted before it sends the notification to peers, it resends it after restart. Possibly - to all peers (then repeated notifications are gracefully handled by the replica) or just to those that didn't get it.
    • If a replica got a notification from a primary instance but did not completed the artifact download and is restarted, it downloads the artifact after the restart.
    • If primary or replica Nexus is restarted during replication, the artifact is re-downloaded after the restart.

It's a fault tolerance extention for #4 and #5.

gd-tmagrys added a commit to gd-tmagrys/nexus-replication-plugin that referenced this issue Jun 29, 2015
gd-tmagrys added a commit to gd-tmagrys/nexus-replication-plugin that referenced this issue Jul 1, 2015
griddynamics#12

Queue with replication requests in now being persisted in file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant