Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

BindException: Address already in use when using kafka-connect with confluent

Highlighted

BindException: Address already in use when using kafka-connect with confluent

New Contributor

Hello eveyrone!

I am using kafka confluent for my project. When I run kafka-connect command, I always get Address already in use response although I don't use 8003 port. Despite I still can use this feature with original kafka. Anyone can help me? Thanks!

1 REPLY 1

Re: BindException: Address already in use when using kafka-connect with confluent

Super Mentor

@Quang_Vu_Blog 

As per kafka-connect docs the default port "rest.port" is 8083 

  • rest.port - the port the REST interface listens on for HTTP requests
 

So are you getting conflict on port 8003 (or there is a typo ? is it 8083) 

Can you try changing the "rest.port" in your worker config to something else and then try again.

Also please try to run the below commands before starting kafka-connect to verify if there is any port conflict? Or if there are any bind address issue

 

# netstat -tnlpa | grep 8083
# netstat -tnlpa | grep 8003

 

.

Don't have an account?
Coming from Hortonworks? Activate your account here