Oops... The "adasdasdasdasd" below is JSON scraped from the status API endpoint.
-Original Message-
From: Wes Holler
Sent: Friday, April 29, 2016 6:09 PM
To: dev
Subject: RPC Timeout and Abnormally Long JvmGcTime
Recently we switched to EMR 4.5/Spark 1.6.1 and have since encountered a ne
Recently we switched to EMR 4.5/Spark 1.6.1 and have since encountered a new
failure scenario.
The primary symptom is that the cluster appears to be stalled. The job has not
failed but will not proceed and has to be killed. One or more
RpcTimeoutException s (see below) are usually found towards
(copy-pasta of previous message)
another project hosted on our jenkins (e-mission) needs anaconda scipy
upgraded from 0.15.1 to 0.17.0. this will also upgrade a few other
libs, which i've included at the end of this email.
i've spoken w/josh @ databricks and we don't believe that this will
impac
Hi,
I have submitted a PR for SPARK-11962 (
https://github.com/apache/spark/pull/12708). I have most of it ready except
I am not able to pin point the cause for a particular bug.
In the PR I've added two major methods to Row, `attempt` and `getOption`.
The former returns a `Try` while the latter
*spark*-unsubscribe-user=rob...@bigfoot.com
