[RTFACT-17484] Pull event replication fails after instance restart Created: 10/Sep/18  Updated: 14/Mar/19  Resolved: 07/Feb/19

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Replication
Affects Version/s: 6.2.0, 6.3.3
Fix Version/s: 6.8.0

Type: Bug Priority: Critical
Reporter: Andrei Komarov Assignee: Inbar Tal
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by RTFACT-17500 Multipush replication does not initia... Resolved
Sprint: Leap 37

 Description   

Pull replication does not re-establish after one of the instances (pull target) restarts.

Applicable for HA as well

Steps to reproduce:

1. Start instance A.
2. Start instance B.
3. Configure local, remote full-mesh event-based pull replication.
4. Upload artifact to instance A, check instance B cache – OK: artifact replicated.
5. Upload artifact to instance B, check instance A cache – OK: artifact replicated.
6. Stop instance A.
7. Start instance A.
8. Upload artifact to instance A, check instance B cache – OK: artifact replicated.
9. Upload artifact to instance B, check instance A cache – FAIL: artifact missing.



 Comments   
Comment by Inbar Tal [ 07/Feb/19 ]

I reproduced this issue on Artifactory version 6.7.0 - configured event pull replication and restart the Artifactory target. Restart the source works just fine.

This issue was fixed by https://www.jfrog.com/jira/browse/RTFACT-17187.
Im closing this issue.

Generated at Sun Nov 17 20:46:50 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.