nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD Transaction Hole

brent1

Have I found a hole in the OD transactional deployment? Here is the sequence of events that seems to be happening:

Start transactional deployment to 3 server web farm (servers A, B, and C)
File transfers complete and Commit phase begins
OD service on server B crashes during commit
Deployment fails due to timeout on server B
Servers A and C do not roll back since they have already committed

Is this possible? Has anyone else experienced this? Is there any way to catch this and repair it?

Much thanks.

Brent
Beckman Coulter Inc.

Find more posts tagged with

Comments

Migrateduser

I think that if a leg fails during the commit phase, the other legs will rollback during the cleanup phase. That is, the .iwold files are renamed back to the original files.

If a failure happens during cleanup after commit, then I think it's too late to roll back since .iwold files will have been removed.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com