What is "round" when replicating components
We are attempting a few tests before our team moves to Jazz 4 to ensure our teams' processes will work. To do this we need a copy of some components to work with from a different repository. I followed the instructions found here:
https://jazz.net/library/article/535/
Smaller components are no problem. However we also have a component with quite a large change set history. Numerous attempts to accept this component into a workspace have failed with various errors, including Out of memory, and some mysterious "Deferred operation failed" errors.
I am mainly interested in a way of telling that we are actually making progress with this. The progress window shows the following message:
Message from https://jazz001.hursley.ibm.com:9443/ccm: Requesting replication data for round 887 from https://jazza03.hursley.ibm.com:9443/ccm/
and stays at 22-23% - Accepting Change sets
Usually when the process fails, on a restart it will fly up to whichever round it failed on and continue. I assumed from this that "round" was an indicator of progress, and that progress was continued from where it failed. What exactly is round? Are these assumptions correct?
Another question would be whether we should expect this process to be as long as it has been. So far we have been attempting re-runs for 4-5 days.
https://jazz.net/library/article/535/
Smaller components are no problem. However we also have a component with quite a large change set history. Numerous attempts to accept this component into a workspace have failed with various errors, including Out of memory, and some mysterious "Deferred operation failed" errors.
I am mainly interested in a way of telling that we are actually making progress with this. The progress window shows the following message:
Message from https://jazz001.hursley.ibm.com:9443/ccm: Requesting replication data for round 887 from https://jazza03.hursley.ibm.com:9443/ccm/
and stays at 22-23% - Accepting Change sets
Usually when the process fails, on a restart it will fly up to whichever round it failed on and continue. I assumed from this that "round" was an indicator of progress, and that progress was continued from where it failed. What exactly is round? Are these assumptions correct?
Another question would be whether we should expect this process to be as long as it has been. So far we have been attempting re-runs for 4-5 days.
Accepted answer
The Accepting Changeset progress will remain at the same level until all required data has been replicated between the servers. The "round" is an indication of progress during replication between servers. I don't believe we know up front how many rounds will be required.
I'm a little fuzzy on the exact details, but the general idea is that server1 will ask server2 for a set of items (ie change sets or baselines it wants to accept) and server2 will send over those items. This is one round.
At the end of a round N, server1 may find that the items it received refer to other items that it does not have. (ex:, ChangeSets refer to Components and Changes, Changes have files/folders, files will have content, Components have a history of other ChangeSets, etc). Server1 will request those missing items from server2, and this will be round N+1.
I don't really have a feel for how much data would be involved in a single round, and whether or not 887 would be considered unusually high for a large component.
I'm a little fuzzy on the exact details, but the general idea is that server1 will ask server2 for a set of items (ie change sets or baselines it wants to accept) and server2 will send over those items. This is one round.
At the end of a round N, server1 may find that the items it received refer to other items that it does not have. (ex:, ChangeSets refer to Components and Changes, Changes have files/folders, files will have content, Components have a history of other ChangeSets, etc). Server1 will request those missing items from server2, and this will be round N+1.
I don't really have a feel for how much data would be involved in a single round, and whether or not 887 would be considered unusually high for a large component.
Comments
2 other answers
It sounds like there might be a problem with replicating the change sets to the other server. This might be a bug. I believe the rounds are a rough form of progress. You can definitely resume the replication and it will continue replicating. The change sets that have been replicated won't be replicated again.