Dear all:
I received a few warning email as below. Does anyone know how should I
avoid those waring email?
Sincerely,
Selina
- -- - - - - - -
Hi! This is the ezmlm program. I'm managing the
dev@samza.apache.org mailing list.
I'm working for my owner, who can be reached
at
Thanks for sharing!
Tao, did you use YARN to run 15 containers or is there a way to have them
statically divide up the tasks?
On Mon, Aug 24, 2015 at 12:03 PM, Ed Yakabosky
eyakabo...@linkedin.com.invalid wrote:
Hi Samza open source,
I want to share that Tao Feng
Hi Raja,
Which OS are you using? I suspect that the OS you are using is Windows.
I see that one of the tests fails with the message:
org.junit.ComparisonFailure:
expected:[/tmp/testing/state/testStore/]Partition_1 but
was:[\tmp\testing\state\testStore\]Partition_1
The only difference is in the
Hi Raja,
The problem is because of a forward slash in the file URL.
testCanReadPropertiesConfigFiles FAILED
java.lang.IllegalArgumentException: Illegal character in authority at
index 7: *file://samza1\samza-core/src/**test/resources/test.properties*
Not sure why it gets generated like that.
Hi Fang,
Still it fails. :(
Regards,
Raja Mahesh Aravapalli.
-Original Message-
From: Yan Fang [mailto:yanfang...@gmail.com]
Sent: Tuesday, August 25, 2015 11:04 AM
To: dev@samza.apache.org
Subject: Re: SAMZA build failing!!!
Hi Raja,
Can you just do
1. clone
Yes! I don't think we have support building samza on Windows.
The reason you see this error is due to getCanonicalPath() in this line -
https://github.com/apache/samza/blob/master/samza-core/src/test/scala/org/apache/samza/config/factories/TestPropertiesConfigFactory.scala#L34
I believe on
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/37604/
---
(Updated Aug. 25, 2015, 11:48 a.m.)
Review request for samza.
Changes
Hi Navina,
I am on windows.
Do you suggest me to build on Linux ??
Thanks.
Regards,
Raja Mahesh Aravapalli.
-Original Message-
From: Navina Ramesh [mailto:nram...@linkedin.com.INVALID]
Sent: Tuesday, August 25, 2015 12:25 PM
To: dev@samza.apache.org
Subject: Re: SAMZA build
Great!
I shall try and keep the forum posted. Thanks.
Regards,
Raja Mahesh Aravapalli.
-Original Message-
From: Navina Ramesh [mailto:nram...@linkedin.com.INVALID]
Sent: Tuesday, August 25, 2015 12:31 PM
To: dev@samza.apache.org
Subject: Re: SAMZA build failing!!!
Yes! I don't
Hi, Chen,
The at-least-once semantics is always guaranteed by committing the offsets
at the last step in the commit. Hence, flushing to local disk, changelog
and output topics always need to succeed before the offsets are committed
to checkpoint. If anything fails in-between, the offset will not
Thanks Navina.
What I found is that containers logs were gone after days locally even when
the job is still running.
Chen
On Mon, Aug 3, 2015 at 6:06 PM, Navina Ramesh nram...@linkedin.com.invalid
wrote:
Hi Chen,
You can set the yarn.nodemanage.delete.debug-delay-sec config in
Also, I have YARN aggregated enabled. But because logs are gone locally,
after the job is killed or failed. I don't have aggregated logs on HDFS.
On Tue, Aug 25, 2015 at 5:39 PM, Chen Song chen.song...@gmail.com wrote:
Thanks Navina.
What I found is that containers logs were gone after days
12 matches
Mail list logo
