I'm glad that you managed to work it out.
As far as I understand, without specifying the `taskmanager.host`, Task
Manager would try to automatically detect what host/ip address should be
advertised to the Job Manager, using which JM can connect to TM. I don't
know what is your network setup, what are the local network cards, firewall
or routing settings, but either of those can lead to some connection
issues. For example your local machine not being accessible via using
127.0.0.1, but "localhost" working fine. This automatically detected
address is logged in the TM logs "TaskManager will use hostname/address
'{}' ({}) for communication", so if it matters to you, you can check what
was the detected address without specifying `taskmanager.host`, and try to
workout what's wrong with it. But it's most likely not a Flink issue.
Best,
Piotrek
niedz., 20 cze 2021 o 16:17 Lei Wang <leiwang...@gmail.com> napisał(a):
> There's enough slots on the jobmanger UI, but the slots are not available.
>
> After i add taskmanager.host: localhost to flink-conf.yaml, it works.
>
> But i don't know why.
>
> Thanks,
> Lei
>
>
> On Fri, Jun 18, 2021 at 6:07 PM Piotr Nowojski <pnowoj...@apache.org>
> wrote:
>
>> Hi,
>>
>> I would start by looking at the Job Manager and Task Manager logs. Take a
>> look if Task Managers connected/registered in the Job Manager and if so, if
>> there were no problems when submitting the job. It seems like either there
>> are not enough slots, or slots are actually not available.
>>
>> Best,
>> Piotrek
>>
>> pt., 18 cze 2021 o 05:53 Lei Wang <leiwang...@gmail.com> napisał(a):
>>
>>> flink 1.11.2 on a single host.
>>>
>>> ./bin/start-cluster.sh and then
>>>
>>> ./bin/flink run examples/streaming/SocketWindowWordCount.jar --hostname
>>> localhost --port 1111
>>>
>>> But on the jobmanager UI, the task is always in created state. There's
>>> available slots.
>>>
>>> Any insights on this?
>>>
>>> Thanks,
>>> Lei
>>>
>>
