discovery.event.pin.jobs The discovery.event.pin.jobs property pins event processors to specific nodes, ensuring that large Discovery jobs are evenly distributed. This setting helps prevent any single app node from becoming overwhelmed, which is crucial for maintaining optimal performance during Discovery operations.
falseThe answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? | When enabled, this property assigns Discovery jobs to specific nodes, limiting job assignment flexibility but improving load distribution across the system. |
|---|---|
| What area does it affect? | Discovery job processing |
| What does the default mean? | The default value is "false", which means this behavior is disabled by default. |
| When should you review it? | Review this property when configuring Discovery settings or optimizing performance after significant changes. |
Raw metadata from the property record.
| Property name | discovery.event.pin.jobs |
|---|---|
| Sys ID | 0e67532f93fbde543836bfa47aba1027 |
| Type | boolean |
| Application | Global |
| Default value | false |
| Description | When true event processors will be pinned to specific nodes. This will ensure that too many large Discovery jobs don't get picked up by a single app node. Setting this to true will have a small impact on Discovery throughput. |
| Updated | 2025-03-17 09:44:33 |
Official references and nearby text excerpts where this property appears.
discoveryOther properties in the same namespace.
discovery.event.separate.cloud.events
When enabled, this property allows Discovery to utilize separate event queues for IP and cloud discoveries, im
discovery.mssql.cluster.instance.postsensor.delete
It allows the system to delete MSSQL instances and related databases from passive cluster nodes after failover
discovery.use.event.processing
This property determines whether Discovery utilizes the Event Framework for processing jobs, which enhances pe