Hey Jeremiah,
That's basically what I mean by "all at once"; ie, a script to submits
multiple tasks in sequence without breaks. I'd be surprised if YARN
couldn't handle that, but just thought I'd ask.
It really looks like it's a problem with the way our infrastructure is
configured. I think I nee
Twitter | Facebook | LinkedIn
From: Malcolm McFarland
Sent: Monday, May 20, 2019 10:49 PM
To: dev@samza.apache.org
Subject: Re: Samza tasks aren't starting in YARN containers
Hey Jagadish,
Thanks for the tip. I'm including the stacktrace for a running, stuc
Hey Jagadish,
Thanks for the tip. I'm including the stacktrace for a running, stuck
process. Usually when I try to restart a single process manually, it
works fine. This brings up the question: are there any
resource-contention issues with submitting multiple jobs to YARN at
once?
Also, I was usi
Can you attach
(1) the full log file for the AM?
(2) the full log file for the container
> Btw, how do I pull a thread-dump of the stuck container?
Should not be any different than a thread dump for a Java process.
Log in to the machine YARN shows the container as running, locate its
process-id
Hey all,
Logs are working, the AM process is running. I haven't hit a "known good
version" yet; the deploy seems to be hitting this wall each time, which,
once again, seems to fail slightly differently each time. Looking at the
node manager logs, I am seeing this line being repeated:
2019-05-10 0
Malcolm,
Did the AM-process come up? If so, can you attach its entire log-file?
"> everything will launch fine one time, and then it will do this
RUNNING-but-no-Samza thing the next."
IIUC, you believe your container is not making progress. If the issue is
recurs, can you attach a thread-dump &
As a followup to this, here's what I see when the Samza app tries to start;
it actually seems to be getting to the run-container script, and then stops:
Kafka version : 0.11.0.2
Kafka commitId : 73be1e1168f91ee2
Error registering AppInfo mbean
Started coordinator stream writer.
sent SetConfig mes
