spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hamstra <m...@clearstorydata.com>
Subject Re: [VOTE] Apache Spark 2.1.1 (RC2)
Date Sat, 01 Apr 2017 20:05:30 GMT
LocalityPlacementStrategySuite hangs -- definitely been seeing that one for
quite awhile, not just with 2.1.1-rc, also with Ubuntu 16.10, and not with
macOS Sierra.

On Sat, Apr 1, 2017 at 12:34 PM, Sean Owen <sowen@cloudera.com> wrote:

> (Tiny nits: first line says '2.1.0', just a note for next copy/paste of
> the email if needed. Also can we point people to an HTTPS URL to download
> artifacts in this boilerplate? https://home.apache.org/~pwendell/spark-
> releases/spark-2.1.1-rc2-bin/ )
>
> I'm testing on Ubuntu 16.10, with Java 8, with -Phive -Pyarn -Phadoop-2.7.
> I am getting several intermittent failures:
>
> - caching in memory, serialized, replicated *** FAILED ***
>   java.util.concurrent.TimeoutException: Can't find 2 executors before
> 30000 milliseconds elapsed
> ...
>
> - caching on disk, replicated *** FAILED ***
>   java.util.concurrent.TimeoutException: Can't find 2 executors before
> 30000 milliseconds elapsed
> ...
>
> - Unpersisting TorrentBroadcast on executors only in distributed mode ***
> FAILED ***
>   java.util.concurrent.TimeoutException: Can't find 2 executors before
> 60000 milliseconds elapsed
> ...
>
> - replicating blocks of object with class defined in repl *** FAILED ***
>   isContain was true Interpreter output contained 'Exception':
> ...
>   scala>      |      | java.util.concurrent.TimeoutException: Executors
> were not up in 60 seconds
> ..
>
> - using external shuffle service *** FAILED ***
>   java.util.concurrent.TimeoutException: Can't find 2 executors before
> 60000 milliseconds elapsed
> ...
>
> LocalityPlacementStrategySuite:
>  (... just hangs ...)
>
>
> Only the last two are persistent. It might be an env issue or test issue,
> so just wondering if anyone else sees these?
>
>
> On Fri, Mar 31, 2017 at 12:09 AM Michael Armbrust <michael@databricks.com>
> wrote:
>
> Please vote on releasing the following candidate as Apache Spark version
> 2.1.0. The vote is open until Sun, April 2nd, 2018 at 16:30 PST and
> passes if a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Spark 2.1.1
> [ ] -1 Do not release this package because ...
>
>
> To learn more about Apache Spark, please see http://spark.apache.org/
>
> The tag to be voted on is v2.1.1-rc2
> <https://github.com/apache/spark/tree/v2.1.1-rc2> (
> 02b165dcc2ee5245d1293a375a31660c9d4e1fa6)
>
> List of JIRA tickets resolved can be found with this filter
> <https://issues.apache.org/jira/browse/SPARK-20134?jql=project%20%3D%20SPARK%20AND%20fixVersion%20%3D%202.1.1>
> .
>
> The release files, including signatures, digests, etc. can be found at:
> http://home.apache.org/~pwendell/spark-releases/spark-2.1.1-rc2-bin/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/pwendell.asc
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-1227/
>
> The documentation corresponding to this release can be found at:
> http://people.apache.org/~pwendell/spark-releases/spark-2.1.1-rc2-docs/
>
>
> *FAQ*
>
> *How can I help test this release?*
>
> If you are a Spark user, you can help us test this release by taking an
> existing Spark workload and running on this release candidate, then
> reporting any regressions.
>
> *What should happen to JIRA tickets still targeting 2.1.1?*
>
> Committers should look at those and triage. Extremely important bug fixes,
> documentation, and API tweaks that impact compatibility should be worked on
> immediately. Everything else please retarget to 2.1.2 or 2.2.0.
>
> *But my bug isn't fixed!??!*
>
> In order to make timely releases, we will typically not hold the release
> unless the bug in question is a regression from 2.1.0.
>
> *What happened to RC1?*
>
> There were issues with the release packaging and as a result was skipped.
>
>

Mime
View raw message