Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connection between overlord and middlemanager #7821

Closed
AzamAhmadloo opened this issue Jun 3, 2019 · 10 comments
Closed

connection between overlord and middlemanager #7821

AzamAhmadloo opened this issue Jun 3, 2019 · 10 comments
Labels

Comments

@AzamAhmadloo
Copy link

AzamAhmadloo commented Jun 3, 2019

Hi.

I installed druid 0.14.1 cluster and now I have an error on my Data server for historical process:

  • ConnectException: Connection refused: localhost/127.0.0.1:8081
  • Caused by: java.net.ConnectException: Connection refused: localhost/127.0.0.1:8081

Now I don't know how to change this localIp (127.0.0.1) to my coordinator server Ip.

@w3z4y4
Copy link

w3z4y4 commented Jun 3, 2019

@AzamAhmadloo
You can add hosts in your cluster.
104.xxx.xxx.xx1 overlord
104.xxx.xxx.xx2 coordinator

@w3z4y4
Copy link

w3z4y4 commented Jun 3, 2019

@AzamAhmadloo
overlord and coordinator log file

@AzamAhmadloo
Copy link
Author

AzamAhmadloo commented Jun 3, 2019

@w3z4y4

Where are log files?
The previous log was log for run command. Do you need this log?

@w3z4y4
Copy link

w3z4y4 commented Jun 3, 2019

@AzamAhmadloo
You can use these command to start Druid~

java `cat conf/druid/coordinator/jvm.config | xargs` -cp conf/druid/_common:conf/druid/coordinator:lib/* org.apache.druid.cli.Main server coordinator > coordinator.log  2>&1 &
java `cat conf/druid/overlord/jvm.config | xargs` -cp conf/druid/_common:conf/druid/overlord:lib/* org.apache.druid.cli.Main server overlord >overlord.log  2>&1 &

@AzamAhmadloo
Copy link
Author

AzamAhmadloo commented Jun 3, 2019

coordinator.log
overlord.log

@w3z4y4
These are log files

@AzamAhmadloo
Copy link
Author

AzamAhmadloo commented Jun 15, 2019

My error on master server fixed. Now my master server see middlemanager server correctly.
I added druid.worker.ip=192.168.0.0 to conf/druid/middlemanager/runtime.properties

The error remains on historical server:

WARN [main] org.apache.druid.discovery.DruidLeaderClient - Request[http://localhost:8081/druid/coordinator/v1/lookups/config/__default?detailed=true] failed.
org.jboss.netty.channel.ChannelException: Faulty channel in resource pool
java.net.ConnectException: Connection refused: localhost/127.0.0.1:8081

How to connect to coordinator server from historical server?

@AzamAhmadloo AzamAhmadloo changed the title connection between overlord and coordinator connection between overlord and middlemanager Jun 15, 2019
@Suroor-Ahmmad
Copy link

Suroor-Ahmmad commented Jul 12, 2019

How did you fix this issue?

@AzamAhmadloo
Copy link
Author

AzamAhmadloo commented Aug 24, 2019

How did you fix this issue?

That was my first view of druid.
You should know zookeeper is incredibly important in your cluster and all your nodes should configure correctly about this.
This is the tip.

@stale
Copy link

stale bot commented May 30, 2020

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

@stale stale bot added the stale label May 30, 2020
@stale
Copy link

stale bot commented Jun 27, 2020

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.

@stale stale bot closed this as completed Jun 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants