[
https://issues.apache.org/jira/browse/PIG-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030993#comment-16030993
]
Nandor Kollar commented on PIG-5245:
------------------------------------
Having this test fixed for MR and for Tez, but not for Spark, can we still
proceed with the release? In my opinion this is not a blocker issue for Spark.
[~kellyzly] [~szita] [~rohini] what do you think? +1 for PIG-5245-2.patch
> TestGrunt.testStopOnFailure is flaky
> ------------------------------------
>
> Key: PIG-5245
> URL: https://issues.apache.org/jira/browse/PIG-5245
> Project: Pig
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.17.0
>
> Attachments: PIG-5245-1.patch, PIG-5245-2.patch
>
>
> The test is supposed to run two tests in parallel, and one when fails other
> should be killed when stop on failure is configured. But the test is actually
> running only job at a time and based on the order in which jobs are run it is
> passing. This is because of the capacity scheduler configuration of the
> MiniCluster. It runs only one AM at a time due to resource restrictions. In a
> 16G node, when the first job runs it takes up 1536 (AM) + 1024 (task)
> memory.mb. Since only 10% of cluster resource is the default for running AMs
> and a single AM already takes up memory close to 1.6G, second job AM is not
> launched.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
