Re: Re: Confused about method naming in heartbeatFromJobManager or heartbeatFromResourceManager

Yes this is how it works. The TaskExecutor gets polled for its heartbeat response if you wish. Of course, if it does not get polled often enough, then the JobMaster or RM can also time out. On Thu, Feb 8, 2018 at 1:22 PM, mingleizhang wrote: > Thanks Till. But sorry,

Re:Re: Confused about method naming in heartbeatFromJobManager or heartbeatFromResourceManager

Thanks Till. But sorry, what what! The TaskExecutor is only responding to heartbeat requests but not actively sending them out ? ? ? I think taskexecutor should report it's status to jobmanager and resourcemanager by heartbeat. And TaskExecutor is like a slave and jobmanager and

Re: Confused about method naming in heartbeatFromJobManager or heartbeatFromResourceManager

The RPC methods `heartbeatFromXYZ` are the incoming heartbeats from the JobMaster and ResourceManager, respectively. That's why they are called heartbeatFrom. The TaskExecutor is only responding to heartbeat requests but not actively sending them out. Cheers, Till On Thu, Feb 8, 2018 at 1:06 PM,

Confused about method naming in heartbeatFromJobManager or heartbeatFromResourceManager

Attached is the taskmanager design picture. And from the picturen, I know taskmanager send heartbeat to jobmanager ( also called jobmaster in flip6 now) and resourcesmanager periodically. But when I watched the source code below in TaskExecutor.java. I feel confused about the function name.