Archiving properties - Paris Release - Support and Troubleshooting

Archiving properties - Paris Release Description Within the Paris release of ServiceNow , Archiving features have been enhanced to provide additional performance and record throughput. As a result it now runs under a producer/consumer model

Records to be archived are now recorded in a queue table in batches and 'sys_archive_run_chunk' is the new queue table

The 'ArchiveProducerJob' creates chunks of sys_ids of records that need to be archived Producer starts up 4 (default) ArchiverJob consumers Consumers read and process rows of sys_ids No guarantee of which rule's records get processed first since the queue is not FIFO Consumers repeat reading rows of sys_ids until there are none left or the limit of rows a consumer can process is hit, after which it will reschedule another consumer and shut down

Resolution In Paris releases onwards the following properties can be used to manipulate the Archive processing:

glide.db.archive.max.batches - max num of rows in queue to process per consumer (default 10) glide.db.archive.chunk_size – max number of sys_ids per batch (default 1000) glide.db.archive.max.rule.records - max records to batch per run per rule (default 10000) glide.db.archiving.max_consumer_workers – max concurrent consumers (default 4) glide.db.archive.chunk.max.process.time - max time a row can be spent processing – (default 600000) <----- This represents milliseconds, which makes it 10 minutes.

These should not be modified without discussions with ServiceNow staff or sub-production validation as increasing them too high could cause performance issues to instances