Uh oh!
There was an error while loading. Please reload this page.
[SPARK-4056] Upgrade snappy-java to 1.1.1.5 - #2911
Conversation
SparkQA
commented
Oct 23, 2014
QA tests have started for PR 2911 at commit
|
rxin
commented
Oct 23, 2014
LGTM. |
SparkQA
commented
Oct 23, 2014
Tests timed out for PR 2911 at commit |
AmplabJenkins
commented
Oct 23, 2014
Test FAILed. |
JoshRosen
commented
Oct 23, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 23, 2014
QA tests have started for PR 2911 at commit
|
JoshRosen
commented
Oct 23, 2014
It looks like these test failures might be due missing classes in the snappy-java 1.1.1.4 JAR: xerial/snappy-java#90 |
SparkQA
commented
Oct 23, 2014
Tests timed out for PR 2911 at commit |
AmplabJenkins
commented
Oct 23, 2014
Test FAILed. |
xerial
commented
Oct 24, 2014
Please use snappy-java-1.1.1.5, which fixes the broken build. |
SparkQA
commented
Oct 24, 2014
QA tests have started for PR 2911 at commit
|
JoshRosen
commented
Oct 24, 2014
@xerial Thanks for fixing that so quickly! |
SparkQA
commented
Oct 24, 2014
Tests timed out for PR 2911 at commit |
AmplabJenkins
commented
Oct 24, 2014
Test FAILed. |
JoshRosen
commented
Oct 24, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 24, 2014
QA tests have started for PR 2911 at commit
|
SparkQA
commented
Oct 24, 2014
QA tests have finished for PR 2911 at commit
|
AmplabJenkins
commented
Oct 24, 2014
Test FAILed. |
xerial
commented
Oct 24, 2014
@JoshRosen If you have the stack trace of this error, please let me know. I would like to check it. |
SparkQA
commented
Oct 24, 2014
QA tests have started for PR 2911 at commit
|
JoshRosen
commented
Oct 24, 2014
@xerial Here's a link to the exception from that most recent test failure: In case that link breaks, here's the driver stacktrace: This isn't the full stacktrace of the actual error, which took place in an executor. Until we merge #2845, I don't think that I'll have an easy way to grab the full executor logs from Jenkins. I wasn't able to reproduce this failure locally. I'm going to try our new experimental "Deflake build" Jenkins button, which reruns only the failing tests, in order to see if I can reproduce this. If so, I'll SSH in and grab the full logs. |
JoshRosen
commented
Oct 24, 2014
Actually, I don't think that "deflake build" plugin will necessarily work as expected given all of the customization in our build; I guess it was added for another project that shares the Jenkins server with us. |
SparkQA
commented
Oct 24, 2014
QA tests have finished for PR 2911 at commit
|
JoshRosen
commented
Oct 24, 2014
Hmm, looks like that might have been a transient failure. Just to be sure, though, I'm going to run this one more time to make sure that it still passes, then merge it (since I don't think that any issues we'll observe will be caused by this small snappy-java version bump). Jenkins, retest this please. |
JoshRosen
commented
Oct 24, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 24, 2014
Test build #22143 has started for PR 2911 at commit
|
AmplabJenkins
commented
Oct 24, 2014
Test FAILed. |
pwendell
commented
Oct 24, 2014
Jenkins, retest this please (sorry I had to abort this to clean the workspace). |
SparkQA
commented
Oct 24, 2014
Test build #22144 has started for PR 2911 at commit
|
SparkQA
commented
Oct 24, 2014
Test build #22144 has finished for PR 2911 at commit
|
AmplabJenkins
commented
Oct 24, 2014
Test FAILed. |
JoshRosen
commented
Oct 24, 2014
The "IOException: unexpected exception type" error here is actually masking the real error; this is due to us throwing something other than IOException from read/writeExternal; I've opened https://issues.apache.org/jira/browse/SPARK-4080 to fix this (working on a patch now). I'm pretty sure that this isn't caused by Snappy, but instead is an instance of some longer-standing non-deterministic serialization issue in our code. |
JoshRosen
commented
Oct 24, 2014
Now that I've fixed the IOException issue via #2932, let's retest this to see if I get a more informative error message. I'm almost positive that this isn't a Snappy issue; I'm just curious to see what happens. Jenkins, retest this please. |
JoshRosen
commented
Oct 24, 2014
Jenkins, retest this please. |
SparkQA
commented
Oct 24, 2014
Test build #22178 has started for PR 2911 at commit
|
SparkQA
commented
Oct 25, 2014
Test build #22178 has finished for PR 2911 at commit
|
AmplabJenkins
commented
Oct 25, 2014
Test FAILed. |
JoshRosen
commented
Oct 25, 2014
Those failures are related to known issues from the Hive 13 PR, not this, so I'm going to merge this across all of our backport branches in order to improve our error reporting. |
This upgrades snappy-java to 1.1.1.5, which improves error messages when attempting to deserialize empty inputs using SnappyInputStream (see xerial/snappy-java#89). Author: Josh Rosen <rosenville@gmail.com> Author: Josh Rosen <joshrosen@databricks.com> Closes#2911 from JoshRosen/upgrade-snappy-java and squashes the following commits: adec96c [Josh Rosen] Use snappy-java 1.1.1.5 cc953d6 [Josh Rosen] [SPARK-4056] Upgrade snappy-java to 1.1.1.4 (cherry picked from commit 898b22a) Signed-off-by: Josh Rosen <joshrosen@databricks.com> Conflicts: pom.xml
JoshRosen
commented
Oct 26, 2014
Since merging this PR, I've started noticing some OOM failures in a test that uses SnappyOutputStream: @xerial do you think there could be a memory leak in the new CachedBufferAllocator? xerial/snappy-java@1.1.1.3...develop |
JoshRosen
commented
Oct 26, 2014
I've reverted this in commit 898b22a until we figure out what's going on. |
We previously tried up upgrade to 1.1.1.5 in apache#2911 but reverted that patch after discovering a memory leak in snappy-java. This should leak have been fixed in 1.1.1.6, though.
This upgrades snappy-java to 1.1.1.6, which includes a patch that improves error messages when attempting to deserialize empty inputs using SnappyInputStream (see xerial/snappy-java#89). We previously tried up upgrade to 1.1.1.5 in #2911 but reverted that patch after discovering a memory leak in snappy-java. This should leak have been fixed in 1.1.1.6, though (see xerial/snappy-java#92). Author: Josh Rosen <joshrosen@databricks.com> Closes#3287 from JoshRosen/SPARK-4419 and squashes the following commits: 5d6f4cc [Josh Rosen] [SPARK-4419] Upgrade snappy-java to 1.1.1.6.
This upgrades snappy-java to 1.1.1.6, which includes a patch that improves error messages when attempting to deserialize empty inputs using SnappyInputStream (see xerial/snappy-java#89). We previously tried up upgrade to 1.1.1.5 in #2911 but reverted that patch after discovering a memory leak in snappy-java. This should leak have been fixed in 1.1.1.6, though (see xerial/snappy-java#92). Author: Josh Rosen <joshrosen@databricks.com> Closes#3287 from JoshRosen/SPARK-4419 and squashes the following commits: 5d6f4cc [Josh Rosen] [SPARK-4419] Upgrade snappy-java to 1.1.1.6. (cherry picked from commit 7d8e152) Signed-off-by: Reynold Xin <rxin@databricks.com>
This upgrades snappy-java to 1.1.1.5, which improves error messages when attempting to deserialize empty inputs using SnappyInputStream (see xerial/snappy-java#89).