Common Content for Data Engineering
- Common Content for Data Engineering 10.5.5.1
- All Products
Property
| Description
|
---|---|
Max Heap Size
| Amount of RAM in megabytes allocated to the Java Virtual Manager (JVM) that runs Metadata Manager. Use this property to increase the performance of Metadata Manager.
For example, you can use this value to increase the performance of Metadata Manager during indexing.
If you create Cloudera Navigator resources, set this property to at least 4096 MB (4 GB).
Default is 4096.
|
Maximum Catalog Child Objects
| Number of child objects that appear in the Metadata Manager metadata catalog for any parent object. The child objects can include folders, logical groups, and metadata objects. Use this option to limit the number of child objects that appear in the metadata catalog for any parent object.
Default is 100.
|
Error Severity Level
| Level of error messages written to the Metadata Manager Service log. Specify one of the following message levels:
When you specify a severity level, the log includes all errors at that level and above. For example, if the severity level is Warning, the log includes fatal, error, and warning messages. Use Trace or Debug if Informatica Global Customer Support instructs you to use that logging level for troubleshooting purposes.
Default is Error.
|
Max Concurrent Resource Load
| Maximum number of resources that Metadata Manager can load simultaneously. Maximum is 10.
Metadata Manager adds resource loads to the load queue in the order that you request the loads. If you simultaneously load more than the maximum, Metadata Manager adds the resource loads to the load queue in a random order. For example, you set the property to 5 and schedule eight resource loads to run at the same time. Metadata Manager adds the eight loads to the load queue in a random order. Metadata Manager simultaneously processes the first five resource loads in the queue. The last three resource loads wait in the load queue.
If a resource load succeeds, fails and cannot be resumed, or fails during the path building task and can be resumed, Metadata Manager removes the resource load from the queue. Metadata Manager starts processing the next load waiting in the queue.
If a resource load fails when the PowerCenter Integration Service runs the workflows and the workflows can be resumed, the resource load is resumable. Metadata Manager keeps the resumable load in the load queue until the timeout interval is exceeded or until you resume the failed load. Metadata Manager includes a resumable load due to a failure during workflow processing in the concurrent load count.
Default is 3.
If you increase the number of maximum concurrent resource loads, increase the number of maximum active connections to the Metadata Manager repository database. For example, if you set this property to 10, Informatica recommends that you also set the
Maximum Active Connections property to 50 or more.
|
Timeout Interval
| Amount of time in minutes that Metadata Manager holds a resumable resource load in the load queue. You can resume a resource load within the timeout period if the load fails when PowerCenter runs the workflows and the workflows can be resumed. If you do not resume a failed load within the timeout period, Metadata Manager removes the resource from the load queue.
Default is 30.
If a resource load fails during the path building task, you can resume the failed load at any time.
|