Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

FAQ: Is it possible to change the port of Blaze Job Monitor application without specifying the Hadoop Data Node Host details?
Answer

No, it is not possible to modify the port of 'Blaze Job Monitor' application without specifying the Hadoop Data Node 'Hostname'/'IP Address'. 

 

'Blaze Job Monitor' URL could be configured in 'Blaze Job Monitor address' attribute under 'Blaze Engine' section of the Hadoop pushdown connection. If the 'Blaze Job Monitor Address' attribute is not configured with explicit host details, 'Blaze Job Monitor' application would be starting in one of the active Hadoop data nodes during the Blaze Engine startup. By default, 9080 would be the port for the 'Blaze Job Monitor' application. ​

 

 blaze_job_monitor_address.jpg


It is possible that 'Blaze Job Monitor' application startup could fail with 'Address binding issues', if another instance of 'Blaze Job Monitor' application is already running in the selected Hadoop data node, most possibly started along with Blaze Engine from a different Informatica Domain or a different DIS in the same Informatica Domain.

 

A Feature Request# BDM-29194 has already been raised for giving provision to modify the Blaze Job Monitor port without defining Hadoop Data Node Hostname. Till the Feature Request is implemented in one of the future versions, as a workaround, to modify the port of 'Blaze Job Monitor', you need to specify valid 'Hadoop Data Node Hostname' along with a new port number.


Blaze_job_monitor_new_port.png 


More Information

 

When we specify a hostname for the 'Blaze Job Monitor' and if that Hadoop data node becomes unavailable, the 'Blaze Job Monitor' component would alone be affected and it would not get started. However, it would not impact other service components like 'Blaze Grid Manager'/'Orchestrator' and hence, the mappings would continue to run without any issues.

 

When the Blaze Job Monitor is not running, logs could not be accessed from the Web console UI. However, the logs could be retrieved from the HDFS location, after completion, or from the local file system of Hadoop data node machines, if the jobs are still in progress. For more information related to finding the location of 'Blaze Tasklet' logs, while running/after completion, refer to the following KB articles:

 




Applies To
Product: Data Engineering Integration(Big Data Management); Data Engineering Quality(Big Data Quality); Enterprise Data Preparation; Enterprise Data Catalog
Problem Type: Configuration; Stability
User Type: Administrator; Developer; Data Analyst; Business Analyst
Project Phase: Implement; Optimize
Product Version: Informatica 10.1.1; HotFix; Informatica 10.2; Informatica 10.2.1; Informatica 10.2.1 Service Pack 1; Informatica 10.2.2
Database:
Operating System:
Other Software:

Reference

Attachments

Last Modified Date:11/6/2019 11:45 PMID:602995
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)