---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35067/
---
(Updated June 15, 2015, 1:42 p.m.)
Review request for samza.
Repository:
Hi Shekar,
a. How do I detect it?
-- You can go to Yarn's monitoring page, usually, localhost:8088. May see
what are running.
b. How do I kill redundant jobs?
-- Just like what you do for any Yarn jobs. *yarn application -kill
applicationId* . If you are using the similar structure as the
Hello,
I have a scenario where for each incoming message, I see 3 corresponding
processed message.
I am suspecting that I may have submitted the same job multiple number of
times to Yarn.
If this is the case,
a. How do I detect it
b. How do I kill redundant jobs?
Could there be other reasons
Thanks, Navina. Those two classes have been there for a while. So I think
this is not really related to JobCoordinator/CoordinatorStream. Will just
create a separate ticket for this. Of course, we can finish it within
SAMZA-614.
Cheers,
Fang, Yan
yanfang...@gmail.com
On Mon, Jun 15, 2015 at
All right. Sorry for bothering. I figured it
out. ApplicationMasterRestServlet is for the RPC and
ApplicationMasterWebServlet is for tracking. The AM dashboard is from the
tracking url, not he RPC url. Maybe we should mention the RPC url in the
doc as well, since not many people realize this.
+1 for adding to the documentation. I didn¹t know about this difference.
This information is perhaps part of the JobCoordinator/CoordinatorStream
documentation - SAMZA-614?
On 6/15/15, 11:27 AM, Yan Fang yanfang...@gmail.com wrote:
All right. Sorry for bothering. I figured it
out.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35067/#review87963
---
@Robert:
Can you please add a unit test in TestKafkaConfig to
