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. Appendix A: Troubleshooting
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Regular Expressions
  18. Appendix D: Command Line Program
  19. Appendix E: Configuring Edge Data Streaming to Work With a ZooKeeper Observer
  20. Appendix F: Glossary

User Guide

User Guide

Load Balancing

Load Balancing

When you deploy a target service on multiple
EDS Node
s,
EDS
uses the round-robin method to distribute the messages across the instances.
EDS
avoids data duplication within the load balanced group of instances by delivering each message to one instance. Deploying a target service on multiple nodes ensures that a large volume of data from multiple sources does not overwhelm a single target service instance.
The following image shows how
EDS
balances the load across HDFS target services that you deployed on three nodes:
The data flow has one source service that publishes data as messages 1, 2, and 3 on the topic called logs. Three instances of a target service receive these messages.
EDS
balances the load as follows:
  1. A source service reads data from the data source and publishes it as three messages over a topic called logs.
  2. Three instances of a target service receive the messages.
  3. The target service is deployed on three nodes for purposes of load balancing.
    EDS
    balances the load across the three instances of the target service in round-robin fashion.
Although
EDS
uses the round-robin method, some instances might receive more messages than other instances.
If one or more instances become inactive,
EDS
removes the inactive instances from load balancing decisions and redistributes the load across the remaining instances.

0 COMMENTS

We’d like to hear from you!