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; } } }

20 minutes to delete an edition

Bowker

TS: 5.0.2
OS: NT 4

To prepare for migrating from 5.0.2 to 5.5.2 I'm trying to clean up editions that we no longer need to retain.

We take editions every day, and for the conversion we only want to keep 2 editions per month. So I'm deleting the other 20ish editions for each month. It's taking about 20 minutes to delete each edition. There are only a few thousand assets (<10,000) in each edition.

If I understand what it's doing when it removes an edition, it updates the next edition with all the changes from the preceding edition. Is there a way to delete 13 editions at one time? or some other way to speed up the process?

At this rate it will take about 2 weeks to clean up and I've only got 4 days.

Find more posts tagged with

Comments

james1

On 5.0.x systems, edition deletes could easily be lengthy operations.

Why are you trying to remove them? You don't have to migrate all editions over, you can selectively migrate only the editions that you want.

-- James

--
James H Koh
Interwoven Engineering

gwen1

We migrated choosing a starting edition. This worked and we did not have the overhead of deleting editions. First edition then is a clone of all the content, so you should start with edition previous to the one with the submit history you need on the 5.5.2 backingstore.

Gwen

Migrateduser

James -
CAUTION! don't delete large numbers of editions at the same time. Edtion deletions queue up batch jobs in the background (use iwstat to verify) and once running, there's no way to purge them out of the batch queue (at least this was our experience in 4.2 on Solaris). I discovered this the hard way; I deleted about 2000 editions one day, then found out about the performance and queuing after the system came down. TS 5.5.x still works the same way, but the performance and underlying metadata handling is so much better as to make it a non-issue.

Also, the edition deletion is a very processor intensive process that used to cause performance issues to the whole system.

These was the main reason we jumped from 4.2 to 5.5.x and even beta'd 5.5.0; to gain the performance improvements that the back-end upgrade provided.