[jira] [Commented] (SPARK-21349) Make TASK_SIZE_TO_WARN_KB configurable

[ https://issues.apache.org/jira/browse/SPARK-21349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080789#comment-16080789 ] Kay Ousterhout commented on SPARK-21349: Out of curiosity, what are the task sizes that you're

[jira] [Commented] (SPARK-21349) Make TASK_SIZE_TO_WARN_KB configurable

[ https://issues.apache.org/jira/browse/SPARK-21349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079746#comment-16079746 ] Kay Ousterhout commented on SPARK-21349: Does that mean we should just raise this threshold for

[jira] [Commented] (SPARK-21349) Make TASK_SIZE_TO_WARN_KB configurable

[ https://issues.apache.org/jira/browse/SPARK-21349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079724#comment-16079724 ] Kay Ousterhout commented on SPARK-21349: Is this a major usability issue (and what's the use case

[jira] [Commented] (SPARK-20219) Schedule tasks based on size of input from ScheduledRDD

[ https://issues.apache.org/jira/browse/SPARK-20219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957253#comment-15957253 ] Kay Ousterhout commented on SPARK-20219: Like [~mridulm80] (as mentioned on the PR) I'm hesitant

[jira] [Assigned] (SPARK-19868) conflict TasksetManager lead to spark stopped

[ https://issues.apache.org/jira/browse/SPARK-19868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout reassigned SPARK-19868: -- Assignee: liujianhui > conflict TasksetManager lead to spark stopped >

[jira] [Resolved] (SPARK-19868) conflict TasksetManager lead to spark stopped

[ https://issues.apache.org/jira/browse/SPARK-19868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19868. Resolution: Fixed Fix Version/s: 2.2.0 > conflict TasksetManager lead to spark

[jira] [Created] (SPARK-20116) Remove task-level functionality from the DAGScheduler

Kay Ousterhout created SPARK-20116: -- Summary: Remove task-level functionality from the DAGScheduler Key: SPARK-20116 URL: https://issues.apache.org/jira/browse/SPARK-20116 Project: Spark

[jira] [Commented] (SPARK-19612) Tests failing with timeout

[ https://issues.apache.org/jira/browse/SPARK-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944181#comment-15944181 ] Kay Ousterhout commented on SPARK-19612: And another:

[jira] [Assigned] (SPARK-19820) Allow users to kill tasks, and propagate a kill reason

[ https://issues.apache.org/jira/browse/SPARK-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout reassigned SPARK-19820: -- Assignee: Eric Liang > Allow users to kill tasks, and propagate a kill reason >

[jira] [Resolved] (SPARK-19820) Allow users to kill tasks, and propagate a kill reason

[ https://issues.apache.org/jira/browse/SPARK-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19820. Resolution: Fixed Fix Version/s: 2.2.0 > Allow users to kill tasks, and propagate a

[jira] [Updated] (SPARK-19820) Allow users to kill tasks, and propagate a kill reason

[ https://issues.apache.org/jira/browse/SPARK-19820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19820: --- Summary: Allow users to kill tasks, and propagate a kill reason (was: Allow reason to be

[jira] [Resolved] (SPARK-16929) Speculation-related synchronization bottleneck in checkSpeculatableTasks

[ https://issues.apache.org/jira/browse/SPARK-16929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-16929. Resolution: Fixed Assignee: jin xing Fix Version/s: 2.2.0 >

[jira] [Updated] (SPARK-19612) Tests failing with timeout

[ https://issues.apache.org/jira/browse/SPARK-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19612: --- Affects Version/s: (was: 2.1.1) 2.2.0 > Tests failing with

[jira] [Reopened] (SPARK-19612) Tests failing with timeout

[ https://issues.apache.org/jira/browse/SPARK-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout reopened SPARK-19612: This seems to be back: saw two recently:

[jira] [Resolved] (SPARK-19567) Support some Schedulable variables immutability and access

[ https://issues.apache.org/jira/browse/SPARK-19567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19567. Resolution: Fixed Assignee: Eren Avsarogullari Fix Version/s: 2.2.0 >

[jira] [Updated] (SPARK-19868) conflict TasksetManager lead to spark stopped

[ https://issues.apache.org/jira/browse/SPARK-19868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19868: --- Target Version/s: 2.2.0 > conflict TasksetManager lead to spark stopped >

[jira] [Resolved] (SPARK-19613) Flaky test: StateStoreRDDSuite.versioning and immutability

[ https://issues.apache.org/jira/browse/SPARK-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19613. Resolution: Cannot Reproduce I'm closing this because, while it had a burst of failures

[jira] [Resolved] (SPARK-19612) Tests failing with timeout

[ https://issues.apache.org/jira/browse/SPARK-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19612. Resolution: Cannot Reproduce Closing this for now because I haven't seen this issue in a

[jira] [Resolved] (SPARK-19988) Flaky Test: OrcSourceSuite SPARK-19459/SPARK-18220: read char/varchar column written by Hive

[ https://issues.apache.org/jira/browse/SPARK-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19988. Resolution: Fixed Assignee: Xiao Li Fix Version/s: 2.2.0 Resolved by

[jira] [Commented] (SPARK-18886) Delay scheduling should not delay some executors indefinitely if one task is scheduled before delay timeout

[ https://issues.apache.org/jira/browse/SPARK-18886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931009#comment-15931009 ] Kay Ousterhout commented on SPARK-18886: Sorry for the slow response here! I realized this is

[jira] [Resolved] (SPARK-11460) Locality waits should be based on task set creation time, not last launch time

[ https://issues.apache.org/jira/browse/SPARK-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-11460. Resolution: Duplicate > Locality waits should be based on task set creation time, not last

[jira] [Resolved] (SPARK-18890) Do all task serialization in CoarseGrainedExecutorBackend thread (rather than TaskSchedulerImpl)

[ https://issues.apache.org/jira/browse/SPARK-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-18890. Resolution: Invalid I closed this because, as [~imranr] pointed out on the PR, these

[jira] [Commented] (SPARK-19565) After fetching failed, success of old attempt of stage should be taken as valid.

[ https://issues.apache.org/jira/browse/SPARK-19565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930910#comment-15930910 ] Kay Ousterhout commented on SPARK-19565: [~jinxing6...@126.com] I closed this because it looks

[jira] [Resolved] (SPARK-19565) After fetching failed, success of old attempt of stage should be taken as valid.

[ https://issues.apache.org/jira/browse/SPARK-19565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19565. Resolution: Duplicate > After fetching failed, success of old attempt of stage should be

[jira] [Commented] (SPARK-19755) Blacklist is always active for MesosCoarseGrainedSchedulerBackend. As result - scheduler cannot create an executor after some time.

[ https://issues.apache.org/jira/browse/SPARK-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930909#comment-15930909 ] Kay Ousterhout commented on SPARK-19755: I'm closing this because the configs you're proposing

[jira] [Resolved] (SPARK-19755) Blacklist is always active for MesosCoarseGrainedSchedulerBackend. As result - scheduler cannot create an executor after some time.

[ https://issues.apache.org/jira/browse/SPARK-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19755. Resolution: Not A Problem > Blacklist is always active for

[jira] [Commented] (SPARK-19990) Flaky test: org.apache.spark.sql.hive.execution.HiveCatalogedDDLSuite: create temporary view using

[ https://issues.apache.org/jira/browse/SPARK-19990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929422#comment-15929422 ] Kay Ousterhout commented on SPARK-19990: Thanks [~windpiger]! > Flaky test:

[jira] [Updated] (SPARK-19990) Flaky test: org.apache.spark.sql.hive.execution.HiveCatalogedDDLSuite: create temporary view using

[ https://issues.apache.org/jira/browse/SPARK-19990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19990: --- Description: This test seems to be failing consistently on all of the maven builds:

[jira] [Commented] (SPARK-19988) Flaky Test: OrcSourceSuite SPARK-19459/SPARK-18220: read char/varchar column written by Hive

[ https://issues.apache.org/jira/browse/SPARK-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929334#comment-15929334 ] Kay Ousterhout commented on SPARK-19988: With some help from [~joshrosen] I spent some time

[jira] [Created] (SPARK-19990) Flaky test: org.apache.spark.sql.hive.execution.HiveCatalogedDDLSuite: create temporary view using

Kay Ousterhout created SPARK-19990: -- Summary: Flaky test: org.apache.spark.sql.hive.execution.HiveCatalogedDDLSuite: create temporary view using Key: SPARK-19990 URL:

[jira] [Updated] (SPARK-19964) Flaky test: SparkSubmitSuite fails due to Timeout

[ https://issues.apache.org/jira/browse/SPARK-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19964: --- Summary: Flaky test: SparkSubmitSuite fails due to Timeout (was: SparkSubmitSuite fails due

[jira] [Comment Edited] (SPARK-19964) Flaky test: SparkSubmitSuite fails due to Timeout

[ https://issues.apache.org/jira/browse/SPARK-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929257#comment-15929257 ] Kay Ousterhout edited comment on SPARK-19964 at 3/17/17 12:54 AM: --

[jira] [Commented] (SPARK-19964) SparkSubmitSuite fails due to Timeout

[ https://issues.apache.org/jira/browse/SPARK-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15929257#comment-15929257 ] Kay Ousterhout commented on SPARK-19964: [~srowen] it looks like this is failing periodically in

[jira] [Updated] (SPARK-19988) Flaky Test: OrcSourceSuite SPARK-19459/SPARK-18220: read char/varchar column written by Hive

[ https://issues.apache.org/jira/browse/SPARK-19988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19988: --- Component/s: SQL > Flaky Test: OrcSourceSuite SPARK-19459/SPARK-18220: read char/varchar

[jira] [Created] (SPARK-19989) Flaky Test: org.apache.spark.sql.kafka010.KafkaSourceStressSuite

Kay Ousterhout created SPARK-19989: -- Summary: Flaky Test: org.apache.spark.sql.kafka010.KafkaSourceStressSuite Key: SPARK-19989 URL: https://issues.apache.org/jira/browse/SPARK-19989 Project: Spark

[jira] [Commented] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927539#comment-15927539 ] Kay Ousterhout commented on SPARK-19803: Awesome thanks! > Flaky

[jira] [Commented] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927263#comment-15927263 ] Kay Ousterhout commented on SPARK-19803: This failed again today:

[jira] [Resolved] (SPARK-18066) Add Pool usage policies test coverage for FIFO & FAIR Schedulers

[ https://issues.apache.org/jira/browse/SPARK-18066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-18066. Resolution: Fixed Assignee: Eren Avsarogullari Fix Version/s: 2.2.0 > Add

[jira] [Reopened] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout reopened SPARK-19803: Assignee: Shubham Chopra (was: Genmao Yu) > Flaky BlockManagerProactiveReplicationSuite

[jira] [Commented] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925353#comment-15925353 ] Kay Ousterhout commented on SPARK-19803: This does not appear to be fixed -- it looks like

[jira] [Updated] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19803: --- Labels: flaky-test (was: ) > Flaky BlockManagerProactiveReplicationSuite tests >

[jira] [Updated] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19803: --- Affects Version/s: (was: 2.3.0) 2.2.0 > Flaky

[jira] [Updated] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19803: --- Component/s: Tests > Flaky BlockManagerProactiveReplicationSuite tests >

[jira] [Resolved] (SPARK-19803) Flaky BlockManagerProactiveReplicationSuite tests

[ https://issues.apache.org/jira/browse/SPARK-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19803. Resolution: Fixed Assignee: Genmao Yu Fix Version/s: 2.2.0 Thanks for

[jira] [Resolved] (SPARK-19276) FetchFailures can be hidden by user (or sql) exception handling

[ https://issues.apache.org/jira/browse/SPARK-19276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19276. Resolution: Fixed Assignee: Imran Rashid Fix Version/s: 2.2.0 >

[jira] [Commented] (SPARK-19796) taskScheduler fails serializing long statements received by thrift server

[ https://issues.apache.org/jira/browse/SPARK-19796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893376#comment-15893376 ] Kay Ousterhout commented on SPARK-19796: Do you think we should (separately) fix the underlying

[jira] [Assigned] (SPARK-19631) OutputCommitCoordinator should not allow commits for already failed tasks

[ https://issues.apache.org/jira/browse/SPARK-19631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout reassigned SPARK-19631: -- Assignee: Patrick Woody > OutputCommitCoordinator should not allow commits for

[jira] [Resolved] (SPARK-19631) OutputCommitCoordinator should not allow commits for already failed tasks

[ https://issues.apache.org/jira/browse/SPARK-19631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19631. Resolution: Fixed Fix Version/s: 2.2.0 > OutputCommitCoordinator should not allow

[jira] [Resolved] (SPARK-13931) Resolve stage hanging up problem in a particular case

[ https://issues.apache.org/jira/browse/SPARK-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-13931. Resolution: Fixed Fix Version/s: 2.2.0 > Resolve stage hanging up problem in a

[jira] [Resolved] (SPARK-19777) Scan runningTasksSet when check speculatable tasks in TaskSetManager.

[ https://issues.apache.org/jira/browse/SPARK-19777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19777. Resolution: Fixed Assignee: jin xing Fix Version/s: 2.2.0 > Scan

[jira] [Updated] (SPARK-19772) Flaky test: pyspark.streaming.tests.WindowFunctionTests

[ https://issues.apache.org/jira/browse/SPARK-19772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19772: --- Labels: flaky-test (was: ) > Flaky test: pyspark.streaming.tests.WindowFunctionTests >

[jira] [Commented] (SPARK-19772) Flaky test: pyspark.streaming.tests.WindowFunctionTests

[ https://issues.apache.org/jira/browse/SPARK-19772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888758#comment-15888758 ] Kay Ousterhout commented on SPARK-19772: [~mengxr][~davies] It looks like this came up a while

[jira] [Created] (SPARK-19772) Flaky test: pyspark.streaming.tests.WindowFunctionTests

Kay Ousterhout created SPARK-19772: -- Summary: Flaky test: pyspark.streaming.tests.WindowFunctionTests Key: SPARK-19772 URL: https://issues.apache.org/jira/browse/SPARK-19772 Project: Spark

[jira] [Resolved] (SPARK-19597) ExecutorSuite should have test for tasks that are not deserialiazable

[ https://issues.apache.org/jira/browse/SPARK-19597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19597. Resolution: Fixed Fix Version/s: 2.2.0 > ExecutorSuite should have test for tasks

[jira] [Closed] (SPARK-4681) Turn on executor level blacklisting by default

[ https://issues.apache.org/jira/browse/SPARK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout closed SPARK-4681. - Resolution: Duplicate This was for the old blacklisting mechanism. The linked JIRAs introduce a

[jira] [Closed] (SPARK-19560) Improve tests for when DAGScheduler learns of "successful" ShuffleMapTask from a failed executor

[ https://issues.apache.org/jira/browse/SPARK-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout closed SPARK-19560. -- Resolution: Fixed Target Version/s: 2.2.0 > Improve tests for when DAGScheduler

[jira] [Commented] (SPARK-19596) After a Stage is completed, all Tasksets for the stage should be marked as zombie

[ https://issues.apache.org/jira/browse/SPARK-19596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881726#comment-15881726 ] Kay Ousterhout commented on SPARK-19596: I agree that this is an issue (although it would be

[jira] [Commented] (SPARK-19698) Race condition in stale attempt task completion vs current attempt task completion when task is doing persistent state changes

[ https://issues.apache.org/jira/browse/SPARK-19698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881688#comment-15881688 ] Kay Ousterhout commented on SPARK-19698: My concern is that there are other cases in Spark where

[jira] [Commented] (SPARK-19698) Race condition in stale attempt task completion vs current attempt task completion when task is doing persistent state changes

[ https://issues.apache.org/jira/browse/SPARK-19698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881564#comment-15881564 ] Kay Ousterhout commented on SPARK-19698: I see -- I agree that everything in your description is

[jira] [Updated] (SPARK-14658) when executor lost DagScheduer may submit one stage twice even if the first running taskset for this stage is not finished

[ https://issues.apache.org/jira/browse/SPARK-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-14658: --- Fix Version/s: 2.2.0 > when executor lost DagScheduer may submit one stage twice even if the

[jira] [Resolved] (SPARK-14658) when executor lost DagScheduer may submit one stage twice even if the first running taskset for this stage is not finished

[ https://issues.apache.org/jira/browse/SPARK-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-14658. Resolution: Duplicate I'm fairly sure this duplicates SPARK-19263, as Mark mentioned on

[jira] [Commented] (SPARK-19263) DAGScheduler should avoid sending conflicting task set.

[ https://issues.apache.org/jira/browse/SPARK-19263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881406#comment-15881406 ] Kay Ousterhout commented on SPARK-19263: Just noting that this was fixed by

[jira] [Comment Edited] (SPARK-19698) Race condition in stale attempt task completion vs current attempt task completion when task is doing persistent state changes

[ https://issues.apache.org/jira/browse/SPARK-19698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881358#comment-15881358 ] Kay Ousterhout edited comment on SPARK-19698 at 2/23/17 9:57 PM: - I think

[jira] [Commented] (SPARK-19698) Race condition in stale attempt task completion vs current attempt task completion when task is doing persistent state changes

[ https://issues.apache.org/jira/browse/SPARK-19698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881358#comment-15881358 ] Kay Ousterhout commented on SPARK-19698: I think this is the same issue as SPARK-19263 -- can you

[jira] [Resolved] (SPARK-19684) Move info about running specific tests to developer website

[ https://issues.apache.org/jira/browse/SPARK-19684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19684. Resolution: Fixed Fix Version/s: 2.2.0 > Move info about running specific tests to

[jira] [Created] (SPARK-19684) Move info about running specific tests to developer website

Kay Ousterhout created SPARK-19684: -- Summary: Move info about running specific tests to developer website Key: SPARK-19684 URL: https://issues.apache.org/jira/browse/SPARK-19684 Project: Spark

[jira] [Resolved] (SPARK-19263) DAGScheduler should avoid sending conflicting task set.

[ https://issues.apache.org/jira/browse/SPARK-19263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19263. Resolution: Fixed Assignee: jin xing Fix Version/s: 1.2.0 > DAGScheduler

[jira] [Created] (SPARK-19613) Flaky test: StateStoreRDDSuite.versioning and immutability

Kay Ousterhout created SPARK-19613: -- Summary: Flaky test: StateStoreRDDSuite.versioning and immutability Key: SPARK-19613 URL: https://issues.apache.org/jira/browse/SPARK-19613 Project: Spark

[jira] [Commented] (SPARK-19612) Tests failing with timeout

[ https://issues.apache.org/jira/browse/SPARK-19612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868565#comment-15868565 ] Kay Ousterhout commented on SPARK-19612: Does that mean we could potentially fix this by limiting

[jira] [Created] (SPARK-19612) Tests failing with timeout

Kay Ousterhout created SPARK-19612: -- Summary: Tests failing with timeout Key: SPARK-19612 URL: https://issues.apache.org/jira/browse/SPARK-19612 Project: Spark Issue Type: Bug

[jira] [Resolved] (SPARK-19537) Move the pendingPartitions variable from Stage to ShuffleMapStage

[ https://issues.apache.org/jira/browse/SPARK-19537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19537. Resolution: Fixed Fix Version/s: 2.2.0 > Move the pendingPartitions variable from

[jira] [Closed] (SPARK-19502) Remove unnecessary code to re-submit stages in the DAGScheduler

[ https://issues.apache.org/jira/browse/SPARK-19502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout closed SPARK-19502. -- Resolution: Not A Problem This code actually is currently needed to handle cases where a

[jira] [Updated] (SPARK-19538) DAGScheduler and TaskSetManager can have an inconsistent view of whether a stage is complete.

[ https://issues.apache.org/jira/browse/SPARK-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19538: --- Priority: Minor (was: Major) > DAGScheduler and TaskSetManager can have an inconsistent

[jira] [Created] (SPARK-19560) Improve tests for when DAGScheduler learns of "successful" ShuffleMapTask from a failed executor

Kay Ousterhout created SPARK-19560: -- Summary: Improve tests for when DAGScheduler learns of "successful" ShuffleMapTask from a failed executor Key: SPARK-19560 URL:

[jira] [Updated] (SPARK-19559) Fix flaky KafkaSourceSuite.subscribing topic by pattern with topic deletions

[ https://issues.apache.org/jira/browse/SPARK-19559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19559: --- Description: This test has started failing frequently recently; e.g.,

[jira] [Created] (SPARK-19559) Fix flaky KafkaSourceSuite.subscribing topic by pattern with topic deletions

Kay Ousterhout created SPARK-19559: -- Summary: Fix flaky KafkaSourceSuite.subscribing topic by pattern with topic deletions Key: SPARK-19559 URL: https://issues.apache.org/jira/browse/SPARK-19559

[jira] [Resolved] (SPARK-19466) Improve Fair Scheduler Logging

[ https://issues.apache.org/jira/browse/SPARK-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19466. Resolution: Fixed Assignee: Eren Avsarogullari Fix Version/s: 2.2.0 >

[jira] [Created] (SPARK-19538) DAGScheduler and TaskSetManager can have an inconsistent view of whether a stage is complete.

Kay Ousterhout created SPARK-19538: -- Summary: DAGScheduler and TaskSetManager can have an inconsistent view of whether a stage is complete. Key: SPARK-19538 URL: https://issues.apache.org/jira/browse/SPARK-19538

[jira] [Created] (SPARK-19537) Move the pendingPartitions variable from Stage to ShuffleMapStage

Kay Ousterhout created SPARK-19537: -- Summary: Move the pendingPartitions variable from Stage to ShuffleMapStage Key: SPARK-19537 URL: https://issues.apache.org/jira/browse/SPARK-19537 Project: Spark

[jira] [Comment Edited] (SPARK-18967) Locality preferences should be used when scheduling even when delay scheduling is turned off

[ https://issues.apache.org/jira/browse/SPARK-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855615#comment-15855615 ] Kay Ousterhout edited comment on SPARK-18967 at 2/7/17 9:42 PM: Please

[jira] [Commented] (SPARK-18967) Locality preferences should be used when scheduling even when delay scheduling is turned off

[ https://issues.apache.org/jira/browse/SPARK-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856842#comment-15856842 ] Kay Ousterhout commented on SPARK-18967: Oops this was me [~rxin] sorry! > Locality preferences

[jira] [Comment Edited] (SPARK-18967) Locality preferences should be used when scheduling even when delay scheduling is turned off

[ https://issues.apache.org/jira/browse/SPARK-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15855615#comment-15855615 ] Kay Ousterhout edited comment on SPARK-18967 at 2/7/17 9:40 PM: Oops this

[jira] [Updated] (SPARK-19502) Remove unnecessary code to re-submit stages in the DAGScheduler

[ https://issues.apache.org/jira/browse/SPARK-19502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19502: --- Description: There are a [few lines of code in the

[jira] [Created] (SPARK-19502) Remove unnecessary code to re-submit stages in the DAGScheduler

Kay Ousterhout created SPARK-19502: -- Summary: Remove unnecessary code to re-submit stages in the DAGScheduler Key: SPARK-19502 URL: https://issues.apache.org/jira/browse/SPARK-19502 Project: Spark

[jira] [Resolved] (SPARK-18967) Locality preferences should be used when scheduling even when delay scheduling is turned off

[ https://issues.apache.org/jira/browse/SPARK-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-18967. Resolution: Fixed Fix Version/s: 2.2 > Locality preferences should be used when

[jira] [Updated] (SPARK-19398) Log in TaskSetManager is not correct

[ https://issues.apache.org/jira/browse/SPARK-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19398: --- Fix Version/s: 2.2 > Log in TaskSetManager is not correct >

[jira] [Resolved] (SPARK-19398) Log in TaskSetManager is not correct

[ https://issues.apache.org/jira/browse/SPARK-19398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19398. Resolution: Fixed Assignee: jin xing > Log in TaskSetManager is not correct >

[jira] [Commented] (SPARK-19326) Speculated task attempts do not get launched in few scenarios

[ https://issues.apache.org/jira/browse/SPARK-19326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852085#comment-15852085 ] Kay Ousterhout commented on SPARK-19326: I see that makes sense; thanks for the additional

[jira] [Commented] (SPARK-19326) Speculated task attempts do not get launched in few scenarios

[ https://issues.apache.org/jira/browse/SPARK-19326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850548#comment-15850548 ] Kay Ousterhout commented on SPARK-19326: What is the bad behavior that occurs with your example

[jira] [Updated] (SPARK-18890) Do all task serialization in CoarseGrainedExecutorBackend thread (rather than TaskSchedulerImpl)

[ https://issues.apache.org/jira/browse/SPARK-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-18890: --- Issue Type: Improvement (was: Bug) > Do all task serialization in

[jira] [Commented] (SPARK-18890) Do all task serialization in CoarseGrainedExecutorBackend thread (rather than TaskSchedulerImpl)

[ https://issues.apache.org/jira/browse/SPARK-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15805495#comment-15805495 ] Kay Ousterhout commented on SPARK-18890: I just opened SPARK-19108 for the broadcast issue. In

[jira] [Created] (SPARK-19108) Broadcast all shared parts of tasks (to reduce task serialization time)

Kay Ousterhout created SPARK-19108: -- Summary: Broadcast all shared parts of tasks (to reduce task serialization time) Key: SPARK-19108 URL: https://issues.apache.org/jira/browse/SPARK-19108 Project:

[jira] [Closed] (SPARK-3937) Unsafe memory access inside of Snappy library

[ https://issues.apache.org/jira/browse/SPARK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout closed SPARK-3937. - > Unsafe memory access inside of Snappy library > - > >

[jira] [Resolved] (SPARK-3937) Unsafe memory access inside of Snappy library

[ https://issues.apache.org/jira/browse/SPARK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-3937. --- Resolution: Won't Fix Closing this due to lack of activity / reports of issues on recent

[jira] [Resolved] (SPARK-14958) Failed task hangs if error is encountered when getting task result

[ https://issues.apache.org/jira/browse/SPARK-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-14958. Resolution: Fixed Fix Version/s: 2.2.0 > Failed task hangs if error is encountered

[jira] [Updated] (SPARK-14958) Failed task hangs if error is encountered when getting task result

[ https://issues.apache.org/jira/browse/SPARK-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-14958: --- Affects Version/s: 1.6.0 2.0.0 2.1.0 > Failed

[jira] [Updated] (SPARK-14958) Failed task hangs if error is encountered when getting task result

[ https://issues.apache.org/jira/browse/SPARK-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-14958: --- Assignee: Rui Li > Failed task hangs if error is encountered when getting task result >

[jira] [Updated] (SPARK-19062) Utils.writeByteBuffer should not modify buffer position

[ https://issues.apache.org/jira/browse/SPARK-19062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19062: --- Affects Version/s: (was: 1.2.1) 2.1.0 > Utils.writeByteBuffer

[jira] [Resolved] (SPARK-19062) Utils.writeByteBuffer should not modify buffer position

[ https://issues.apache.org/jira/browse/SPARK-19062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout resolved SPARK-19062. Resolution: Fixed Fix Version/s: 2.2.0 > Utils.writeByteBuffer should not modify

[jira] [Updated] (SPARK-19072) Catalyst's IN always returns false for infinity

[ https://issues.apache.org/jira/browse/SPARK-19072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Ousterhout updated SPARK-19072: --- Description: This bug was caused by the fix for SPARK-18999

  1   2   3   4   >