beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1802) Spark Runner does not shutdown correctly when executing multiple pipelines in sequence
Date Sat, 25 Mar 2017 08:14:41 GMT


ASF GitHub Bot commented on BEAM-1802:

GitHub user aviemzur opened a pull request:

    [BEAM-1802] Stop Spark context on terminal pipeline state

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull stop-terminal-spark-pipelines

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2327
commit 70ba7a5a81046100d3b49a8971febcd089cc3573
Author: Aviem Zur <>
Date:   2017-03-25T08:10:35Z

    [BEAM-1802] Stop Spark context on terminal pipeline state


> Spark Runner does not shutdown correctly when executing multiple pipelines in sequence
> --------------------------------------------------------------------------------------
>                 Key: BEAM-1802
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Ismaël Mejía
>            Assignee: Aviem Zur
> I found this while running the Nexmark queries in sequence in local mode. I had the correct
configuration but it didn't seem to work.
> 17/03/24 12:07:49 WARN org.apache.spark.SparkContext: Multiple running SparkContexts
detected in the same JVM!
> org.apache.spark.SparkException: Only one SparkContext may be running in this JVM (see
SPARK-2243). To ignore this error, set spark.driver.allowMultipleContexts = true. The currently
running SparkContext was created at:
> org.apache.beam.runners.spark.translation.SparkContextFactory.createSparkContext(
> org.apache.beam.runners.spark.translation.SparkContextFactory.getSparkContext(
> org.apache.beam.integration.nexmark.NexmarkDriver.runAll(
> org.apache.beam.integration.nexmark.drivers.NexmarkSparkDriver.main(
> 	at org.apache.spark.SparkContext$$anonfun$assertNoOtherContextIsRunning$1.apply(SparkContext.scala:2257)
> 	at org.apache.spark.SparkContext$$anonfun$assertNoOtherContextIsRunning$1.apply(SparkContext.scala:2239)

This message was sent by Atlassian JIRA

View raw message