ClearCase Sync: Missing Files to synchronize
I had 4 sync jobs configured and running successfully for several weeks. Today I was notified that they were no longer working and when I check the "Files to synchronize" dialog with "Show currently synchronized objects in the table" checked, the list was empty. The same was true for all 4 sync jobs.
I've seen this before and it's easy to recreate the list but also painful due to the time it takes to run another sync (several hours per job in my case).
Where is the list stored? How can I explain it gone missing? What can I do to determine what's going on?
I've seen this before and it's easy to recreate the list but also painful due to the time it takes to run another sync (several hours per job in my case).
Where is the list stored? How can I explain it gone missing? What can I do to determine what's going on?
3 answers
There's a good chance that you ran into bug 102044 (sync roots removed
when view is not accessible) or bug 102650 (sync roots removed when VOB
is not mounted).
Is it possible that the view became inaccessible to the sync host
machine, or that the VOB's containing the sync roots were unmounted from
the sync host machine? We have a fix for the first case, but not for
the second (so we're interested in which case you ran into).
Unfortunately, the only way to recover is to re-add the sync-roots,
which as you point out, causes the next sync to be very slow (as it
verifies that no files have changed between the time the sync roots were
removed and when you added them back).
Cheers,
Geoff
eanderso wrote:
when view is not accessible) or bug 102650 (sync roots removed when VOB
is not mounted).
Is it possible that the view became inaccessible to the sync host
machine, or that the VOB's containing the sync roots were unmounted from
the sync host machine? We have a fix for the first case, but not for
the second (so we're interested in which case you ran into).
Unfortunately, the only way to recover is to re-add the sync-roots,
which as you point out, causes the next sync to be very slow (as it
verifies that no files have changed between the time the sync roots were
removed and when you added them back).
Cheers,
Geoff
eanderso wrote:
I had 4 sync jobs configured and running successfully for several
weeks. Today I was notified that they were no longer working and
when I check the "Files to synchronize" dialog with
"Show currently synchronized objects in the table" checked,
the list was empty. The same was true for all 4 sync jobs.
I've seen this before and it's easy to recreate the list but also
painful due to the time it takes to run another sync (several hours
per job in my case).
Where is the list stored? How can I explain it gone missing? What
can I do to determine what's going on?
Thanks Geoff, it must have been one of these though I can't be sure which.
We're not intentionally unmounting vobs on the sync host, but I have seen cases (infrequent) where a vob is not auto mounted when the view starts. We will address this by mounting the vob(s) on startup (before the jbe starts).
Occasionally ClearCase environment is down for maintenance or has an unplanned outage (very rare). In the case of a planned outage, I'll disable the sync jobs until cc is back. In the case of unplanned, I think the best I can do it check the jobs and fixup if necessary.
We'd like use the plain java api to write a tool to monitor our sync jobs. Do you know if there's enough functionality in the api to check a sync job for this case (an empty sync list)?
We're not intentionally unmounting vobs on the sync host, but I have seen cases (infrequent) where a vob is not auto mounted when the view starts. We will address this by mounting the vob(s) on startup (before the jbe starts).
Occasionally ClearCase environment is down for maintenance or has an unplanned outage (very rare). In the case of a planned outage, I'll disable the sync jobs until cc is back. In the case of unplanned, I think the best I can do it check the jobs and fixup if necessary.
We'd like use the plain java api to write a tool to monitor our sync jobs. Do you know if there's enough functionality in the api to check a sync job for this case (an empty sync list)?
By an "empty sync list", you mean one with no files or folders selected
for synchronization? If so, the easiest way to get this info is
probably through the CC Synchronizer command line tool. In the Eclipse
client on-line help, search for "clearcase connector command line".
Cheers,
Geoff
eanderso wrote:
for synchronization? If so, the easiest way to get this info is
probably through the CC Synchronizer command line tool. In the Eclipse
client on-line help, search for "clearcase connector command line".
Cheers,
Geoff
eanderso wrote:
Thanks Geoff, it must have been one of these though I can't be sure
which.
We're not intentionally unmounting vobs on the sync host, but I have
seen cases (infrequent) where a vob is not auto mounted when the view
starts. We will address this by mounting the vob(s) on startup
(before the jbe starts).
Occasionally ClearCase environment is down for maintenance or has an
unplanned outage (very rare). In the case of a planned outage, I'll
disable the sync jobs until cc is back. In the case of unplanned, I
think the best I can do it check the jobs and fixup if necessary.
We'd like use the plain java api to write a tool to monitor our sync
jobs. Do you know if there's enough functionality in the api to
check a sync job for this case (an empty sync list)?