Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Change the maxTaskFailures depending on property #186

Merged
merged 2 commits into from
Dec 6, 2019

Conversation

suranjan
Copy link

The local propery is set based on plan from snappy side
If the propery is set, then maxTaskFailures is set to the set value

What changes were proposed in this pull request?

(Please fill in changes proposed in this fix)

How was this patch tested?

(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Please review http://spark.apache.org/contributing.html before opening a pull request.

	The local propery is set based on plan from snappy side
	If the propery is set, then maxTaskFailures is set to the set value
@suranjan suranjan requested review from sumwale and kneeraj November 29, 2019 06:10
@suranjan suranjan merged commit 840a4b3 into snappy/branch-2.1 Dec 6, 2019
sumwale pushed a commit to sumwale/spark that referenced this pull request Nov 5, 2020
…oftware#186)

The local propery is set based on plan from snappy side.
If the propery is set, then maxTaskFailures is set to the given value.
sumwale pushed a commit that referenced this pull request Jul 11, 2021
The local propery is set based on plan from snappy side.
If the propery is set, then maxTaskFailures is set to the given value.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant