Skip to content

ERROR: transport error 202: bind failed: Address already in use #119

Description

@VisheshSood

Hi,

I am trying to follow the steps to set up the example given in the project, with a local Zookeeper and a 3 Broker Kafka Cluster (running on a single node). I have another identical set up on a different VM, and using MirrorMaker I am able to produce and consume events. My Kafka topics are stored under a kafka directory in ZK (not cluster1/cluster2 as mentioned in the example).

When I tried to follow the instructions for setting up uReplicator, I am receiving the following error:

 0.009: [G1Ergonomics (Heap Sizing) expand the heap, requested expansion amount: 268435456 bytes, attempted expansion amount: 268435456 bytes]
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]

I used the following command to set up the controller on port 9200 (since 9000 is already used by another service):
./uReplicator-Distribution/target/uReplicator-Distribution-pkg/bin/start-controller.sh -zookeeper localhost:2181/kafka -srcKafkaZkPath {vm-ip}:2181/kafka -destKafkaZkPath localhost:2181/kafka -helixClusterName testMirrorMaker -backUpToGit false -port 9200 -localBackupFilePath /var/log/kafka-mirror-maker-controller -autoRebalanceDelayInSeconds 120
Through this, I am able to start the controller just fine.

After this, I try to set up the worker, using the following command:
./uReplicator-Distribution/target/uReplicator-Distribution-pkg/bin/start-worker.sh --consumer.config mirror/consumer-dev.config --producer.config mirror/producer-dev.config --helix.config config/helix.properties
My helix.properties file looks like the following:

 zkServer=localhost:2181/kafka
 instanceId=testHelixMirrorMaker01
 helixClusterName=testMirrorMaker

I use the same config files that I had for mirror maker (that worked) and I get the error mentioned above. Has anyone seen this issue, or know how to solve it? I even tried to kill all the processes that are running on the ports required by the worker (5005, 9200) but that also kills the Controller service. Am I setting this up incorrectly? Are there other ports that I should be checking for too?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions