Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Edge Data Streaming
  3. Licenses
  4. Using Informatica Administrator
  5. Creating and Managing the Edge Data Streaming Service
  6. Edge Data Streaming Entity Types
  7. Edge Data Streaming Nodes
  8. Data Connections
  9. Working With Data Flows
  10. Managing the Edge Data Streaming Components
  11. Security
  12. High Availability
  13. Disaster Recovery
  14. Monitoring Edge Data Streaming Entities
  15. Troubleshooting
  16. Frequently Asked Questions
  17. Regular Expressions
  18. Command Line Program
  19. Configuring Edge Data Streaming to Work With a ZooKeeper Observer
  20. Glossary

User Guide

User Guide

Troubleshooting Monitoring Tab Views

A EDS Node appears inactive on the Monitoring tab of the Administrator tool.
A EDS Node appears inactive in the following situations:
  • The EDS Node might not be running. Verify the status of the EDS Node. If the EDS Node is not running, start it.
    If the EDS Node is running, navigate to the following directory:
    <EDS Node Installation Directory>/node/logs/
    View the <node name>-node.log file for exceptions and correct them.
  • The Administrator Daemon might not be running. Verify the status of the Administrator Daemon. If the Administrator Daemon is not running, start it.
    If the Administrator Daemon is running, navigate to the following directory:
    <Administrator Daemon Installation Directory>/admind/logs/
    Check the admind.log file for exceptions and correct them.
  • The EDS Node is configured incorrectly.
    Navigate to the following directory:
    <EDS Node Installation Directory>/node/config/
    Verify that the zkservers field in the node.cnf file is pointing to the correct Apache ZooKeeper server URL.
A source service or a target service appears inactive on the Monitoring tab.
This can occur if the source service or a target service is configured incorrectly.
Navigate to the following directory:
<EDS Node Installation Directory>/node/logs/
View the <node name>-node.log file exceptions in source or target, and correct them.
The monitoring data indicates that the source statistics are increasing continuously, but the target statistics received are not increasing.
This error occurs in the following situations:
  • The Topic resolution type field is set to Unicast in the data flow properties, and LBMRD is not running on the address specified in the Resolver daemon field. In the Data Flows pane, click the data flow whose properties you want to view. The Entity Details pane appears. Click Connections tab and click the connection. Verify that LBMRD is running on the address specified in the Resolver daemon field.
  • The Topic resolution field is set to Multicast in the data flow properties, and the source service and target service are on different machines. Verify that the machines running the source service and target service have multicast enabled. Also verify that the machines are configured in the same multicast group.
  • The transformation might not be applied correctly. Verify that you have configured the transformation correctly.
To determine whether multicast is enabled in your environment, perform the multicast capability test.
For more information about the multicast capability test, see the article Informatica MTools on MySupport at https://community.informatica.com/solutions/1470.
I use a Static File source service in my data flow and have specified the processed file directory. The files have been moved to the processed file directory, but the data is not received by the target service.
This situation occurs when the data is not sent to the target service because the files have been ignored. The Static File source service moves the files sent to the target service and the ignored files to the processed file directory. The Static File source service ignores the files in the following situations:
  • The delimiter is EOF and the value of the Maximum Event Size property is less than the size of the file the source service is reading from.
  • The files are older than the files already processed by the Static File source service.
The transformation statistics in the Grid view of the Administrator tool show a higher value in the events received column compared to the value in the events sent column.
This discrepancy might occur when the source service splits the events into multiple events based on the delimiter settings that you have specified for the source service. When the transformation receives the events from the source service, it also includes the split events in the events received statistic. As a result, the events received column of the transformation table displays a higher value than the value that appears in the events sent column of the source entity table.
You can ignore the difference in values as it has no impact on the functionality of the source service.
The monitoring data indicates that the Bytes Received, Events Received, Bytes Sent, and Events Sent statistics are displaying less than expected values.
This behavior occurs if you restart the EDS Node that the source service or target service is associated with. There is no workaround for this behaviour.


Updated March 19, 2019


Explore Informatica Network