This message was deleted.
# general
s
This message was deleted.
b
you should look at the coordinator log and historical logs to determine what is going wrong with the load process.
s
@TRUSHNA SHARMAD PHADKE Are you just deploying Druid locally on your laptop? If so, requesting Max tasks:3 is too many for the quickstart deployment. It is configured for a max of 2 tasks. When I try to run with 3 tasks it shows me this message:
If I run it anyway, it still finishes and uses only 2 tasks. It was done in 18 seconds. What is different about what you see? I tested with version 25.0.0
t
@Sergio Ferragut I have installed it on VM, with version 25.0.0 only, it allowed me to run with setting of max 3 tasks, (earlier by default it was set to max task 2) I changed it when it took similar kind of time with max task 2 setting. I tried running it , but there is no result it is still running, its been 70 hours now
@Bibek Sahoo ,I am checking logs under log folder, log/historical.log, Sharing the snaps of log files (the task is running since 5th may), can you guide me what could be the cause and how can we resolve it.
b
The error “Address already in use” says there is already a service running and you want to start again a service in the same port.
Should we cancel the job and wait for the data source to be fully available
and then check logs for any error
t
yeah, how can I check id data source is fully available?
In coordinator, I also get to see , I have no server message
b
As it is not finding the coordinator, it wont proceed ahead, should we stop and start the server?
t
I tried that roo
b
If you navigate to druid console and ser ices page, do you see coordinator listed their?
t
Let me check that
Are you talking about this ?
b
Check here if coordinator service(Leader) is available
t
okay
seeing some
b
I do not see Historical service being run here, Can you check the logs for historical and try to start the historical service.
t
I am seeing below error in the historical file
s
The default port for the historical service is 8083, Since the router is already bound to 8888, the historical is unable to start. Is there a reason for using a different port on the historical?