https://issues.apache.org/jira/browse/SAMZA-851 and pull request that adds
optional Maven profile
On Wed, Jan 6, 2016 at 5:28 PM, Yi Pan wrote:
> Glad to hear that it has worked. Yeah, I guess right now, if there is any
> dependency conflicts, your solution would be the way to resolve it.
>
> Co
Glad to hear that it has worked. Yeah, I guess right now, if there is any
dependency conflicts, your solution would be the way to resolve it.
Could you open a JIRA to enhance the hello-samza tutorial docs to address
this issue?
Thanks!
-Yi
On Wed, Jan 6, 2016 at 12:47 PM, Stanislav Los
wrote:
So, for now, I made it work by replacing any generic hadoop-* jar in
hello-samza distribution with related jar from CDH:
[stanis...@hcm001.us-east-1.mgnt.cc samza]$ ls -l deploy/samza-cdh/lib/ |
grep hadoop
-rwxr-xr-x 1 stanislav stanislav21533 Jan 6 15:19
hadoop-annotations-2.6.0-cdh5.4.0.j
Token expiration is still a problem w/o Kerberos in YARN 2.6.0 client. But
the exception stack trace from that bug is also different from yours. I am
suspecting there is some incompatible dependency libraries between CDH5.4
distro and Samza that caused your serialization problems here.
On Wed, Jan
Hi Yi,
Our cluster doesn't have Kerberos security in place, so I don't know how it
could be related.
CDH5.4 runs on YARN 2.6.0.
I compiled Samza with YARN 2.6.0 and YARN 2.6.1.
In both cases I get the same error.
Should token expiration be a problem for the cluster without Kerberos?
Regards.
On
Hi, Stanislav,
Could it be related to SAMZA-727? Your exception stack trace is different
though. Besides that, Samza 0.10 requires minimum YARN 2.6.1 now, due to a
token expiration issue in YARN 2.6.0 client lib.
-Yi
On Wed, Jan 6, 2016 at 7:52 AM, Stanislav Los
wrote:
> Hi,
>
> Any ideas why
