Property reference

glide.db.archiving.max_consumer_workers

Limits archive processing to a configured number of concurrent consumers across the cluster. The default is four, so changing the limit changes how many archive consumers can work at once.

Default
Not stated
Type
Not stated
Application
Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do? Sets the maximum number of archive consumers that can run concurrently across the cluster; the default limit is four.
What area does it affect? Archive processing
What does the default mean? No default value is stated in the ServiceNow documentation.
When should you review it? When adjusting cluster-wide archive processing concurrency.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name glide.db.archiving.max_consumer_workers
Type Not stated
Application Not stated
Default value Not stated
Description Not stated

Sources

Official references and nearby text excerpts where this property appears.

Context preview Snippet 1
... table. glide.db.archive.max.batches Number of chunks, which are records from the Archive Job Execution Chunks [sys_archive_run_chunk] table, processed by a consumer before it shuts down and schedules another consumer. Integer 10 glide.db.archiving.max_consumer_workers The maximum number of concurrent consumers cluster- wide. Integer 4 Table cleaner properties To set table cleaner system properties, navigate to the System Properties [sys_properties] table and add the property. ...

More in glide.db

Other properties in the same namespace.

All 82 properties in glide.db →