Druid coordinator&overlord can not start

hello ! everyone
I install druid with Ambari. Then,My metadata storage is mysql.

When I installed druid , everything seems like ok!

But I found coordinator and overlord port not listen.

This is my error!

Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py", line 44, in <module>
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 375, in execute
  File "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py", line 30, in service_check
    self.checkComponent(params, "druid_coordinator", "druid-coordinator")
  File "/var/lib/ambari-agent/cache/common-services/DRUID/0.10.1/package/scripts/service_check.py", line 40, in checkComponent
  File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166, in __init__
  File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 124, in run_action
  File "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line 262, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72, in inner
    result = function(command, **kwargs)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102, in checked_call
    tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150, in _call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 303, in _call
    raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o /dev/null -w'%{http_code}' --negotiate -u: -k ip-172-31-1-91.ap-northeast-1.compute.internal:8081/status | grep 200' returned 1.

Then, when I change metadata storage to derby that it can work!

Does anyone know this problem.

Did you do the database test in Ambari once you selected MySql? There is a chance Druid node is unable to reach out to MySql.

Try connecting as druid user in Mysql from the node where the masters are installed.

Thanks & Rgds


Hi! Venkat!

I had installed mysql and druid in the same node and no alert message.

By and large, it should be work!

But it still not work.

And… how to check if Druid node is able to reach out to MySql?

Thanks & Rgds


Venkat Poornalingam於 2019年4月9日星期二 UTC+8下午3時31分30秒寫道:

Ok. Logon to the druid master node and do

mysql -u druid -p druid

And enter the druid user password.

If mysql is in another node, then supply -h hostname also.

I have check it.

I can connect mysql with druid user and password.

In addition, I found that Ambari have error “Check Druid” when restart it.

Similarly, when I change metadata store as MySQL is not work.

Then, Derby is still work!

I don’t know how to solve…

Venkat Poornalingam於 2019年4月9日星期二 UTC+8下午4時09分12秒寫道:

Ok I think you should go to Druid configs and change the db from Derby to MySql.

Check druid logs present in location /var/log/druid/
I guess it might be either due to mysql permissions not being set properly or the database encoding not being UTF-8.

Ensure that the db encoding is set to utf-8 as per http://druid.io/docs/latest/development/extensions-core/mysql.html