.@ymail.com>>
Date: Thursday, September 29, 2016 at 4:58 AM
To: Hitesh Shah mailto:hit...@apache.org>>
Cc: "user@tez.apache.org<mailto:user@tez.apache.org>"
mailto:user@tez.apache.org>>
Subject: Re: Zip Exception since commit da4098b9
Well, don't see much in
AM
To: Hitesh Shah mailto:hit...@apache.org>>
Cc: "user@tez.apache.org<mailto:user@tez.apache.org>"
mailto:user@tez.apache.org>>
Subject: Re: Zip Exception since commit da4098b9
Well, don't see much in yarn logs
However, in the browser console of tez-ui we see:
>>
The RM will need CORS support turned on so that the Tez UI can query the
live Tez AM from the Tez UI. This support was added in Hadoop 2.7.2.
https://hadoop.apache.org/docs/current2/hadoop-project-dist/hadoop-common/HttpAuthentication.html
On Wed, Sep 28, 2016 at 6:28 PM, Madhusudan Ramanna
wrot
Well, don't see much in yarn logs
However, in the browser console of tez-ui we see:
LHttpRequest cannot load
http://rm:8088/proxy/application_1475091857089_0021/ws/v1/tez/dagProgress?dagID=1&_=1475104772228.
No 'Access-Control-Allow-Origin' header is present on the requested resource.
Ok thanks - so it does look it is publishing data correctly for the most part.
You may wish to start digging through the yarn app logs for which data is not
showing up as well as the yarn timeline logs to see if there are any exceptions
being thrown.
— Hitesh
> On Sep 28, 2016, at 2:50 PM,
Here is history.txt.appattempt_1475091857089_0015_01 (clipped)
{"entity":"tez_application_1475091857089_0015","entitytype":"TEZ_APPLICATION","otherinfo":{"user":"apxqueue","config":""}{"entity":"tez_appattempt_1475091857089_0015_01","entitytype":"TEZ_APPLICATION_ATTEMPT","relatedEntities":
To pinpoint the issue, one approach would be to change the history logger to
SimpleHistoryLogger . i.e comment out the property for
tez.history.logging.service.class in the configs so that it falls back to the
default value. This should generate a history log file as part of the
application log
Hello Madhusudan,
Thanks for the patience. Let us take this to a jira where once you attach more
logs, we can root cause the issue.
A few things to attach to the jira:
- yarn-site.xml
- tez-site.xml
- hadoop version
- timeline server log for the time period in question
- applicat
tez-dist tar balls are not published to maven today - only the module specific
jars are. But yes, you could just try a local build to see if you can reproduce
the issue with the commit in question.
— Hitesh
> On Sep 23, 2016, at 6:23 PM, Madhusudan Ramanna wrote:
>
> Hitesh and Zhiyuan,
>
Hitesh and Zhiyuan,
Apache snapshots doesn't seem to have tez-dist
http://repository.apache.org/content/groups/snapshots/org/apache/tez/tez-dist/
The last one seems to be 0.2.0-SNAPSHOT
Should I just download based on the commit and recompile ?
thanks,Madhu
On Friday, September 23, 2016 5:1
Hello Madhusudan,
If you look at the MANIFEST.MF inside any of the tez jars, it will provide the
commit hash via the SCM-Revision field.
The tez client and the DAGAppMaster also log this info at runtime.
— Hitesh
> On Sep 23, 2016, at 4:08 PM, Madhusudan Ramanna wrote:
>
> Zhiyuan,
>
> We
Hi Madhu,
That’s weird. ShuffleVertexManager was refactored before TEZ-3163 was
committed, and handleVertexManagerEvent was moved to ShuffleVertexManagerBase,
but your stacktrace shows it’s still in ShuffleVertexManager.
I suggest checking tez jar version on both client and server. To find the t
Zhiyuan,
We just pulled down the latest snapshot from Apache repository. Question, is
how can I figure out branch and commit information from the snapshot artifact ?
thanks,Madhu
On Friday, September 23, 2016 10:38 AM, zhiyuan yang
wrote:
Hi Madhu,
It looks like a Inflater-Deflater m
> If you have a simple dag/job example that reproduces the behavior that would
> be great too.
…
>> Caused by: java.util.zip.ZipException: incorrect header check
>> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:164)
>> at java.io.FilterInputStream.read(FilterInputS
Hello Madhusudan
Thanks for reporting the issue. Would you mind filing a bug at
https://issues.apache.org/jira/browse/tez with the application logs and tez
configs attached? If you have a simple dag/job example that reproduces the
behavior that would be great too.
thanks
— Hitesh
> On Sep 23
Hi Madhu,
It looks like a Inflater-Deflater mismatch to me. From stack traces I see you
cherry-picked this patch instead of using master branch.
Would you mind double check whether the patch is correctly cherry-picked?
Thanks!
Zhiyuan
> On Sep 23, 2016, at 10:21 AM, Madhusudan Ramanna wrote:
>
Hello,
We're using the Apache snapshot repository to pull latest tez snapshots.
We've started seeing this exception:
org.apache.tez.dag.api.TezUncheckedException: java.util.zip.ZipException:
incorrect header check
at
org.apache.tez.dag.library.vertexmanager.ShuffleVertexManager.handleVertexManag
17 matches
Mail list logo
