-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-33717][LAUNCHER] deprecate spark.launcher.childConectionTimeout #30679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
For API deprecation, we should file a JIRA, @jsoref. Can you file a JIRA at https://issues.apache.org/jira/projects/SPARK/issues? Also it's best to keep the PR titles properly. See also https://spark.apache.org/contributing.html |
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
|
@HyukjinKwon: I filed https://issues.apache.org/jira/browse/SPARK-33717... @srowen is there something I need to do to push this along? |
|
Jenkins test this please |
|
Test build #136266 has finished for PR 30679 at commit
|
|
@srowen: sigh. can you provide the error output? (I can't find it from the bot's link) (and also the other bot killed this PR) |
|
See the output linked above. It seems to be: |
5650822 to
e1db9f4
Compare
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #136293 has finished for PR 30679 at commit
|
|
Can someone please whack the bot? This is insane. |
|
I cleared the 'stale' tag - that was the issue |
|
Test build #136319 has started for PR 30679 at commit |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Jenkins retest this please |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #136353 has finished for PR 30679 at commit
|
srowen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more thing would finish this out. Let's add a note in docs/core-migration-guide.md, under the 3.1 -> 3.2 heading, like:
In Spark 3.2, spark.launcher.childConectionTimeout is deprecated (typo) though still works. Use spark.launcher.childConnectionTimeout instead.
launcher/src/main/java/org/apache/spark/launcher/SparkLauncher.java
Outdated
Show resolved
Hide resolved
in favor of spark.launcher.childConnectionTimeout Signed-off-by: Josh Soref <[email protected]>
e1db9f4 to
056d432
Compare
|
Unrelated, markdownlint (triggered automatically in VSCode) suggests changing |
|
Probably so - we can think about that separately if it's a problem. |
|
Jenkins retest this please |
|
Test build #136415 has finished for PR 30679 at commit
|
|
Kubernetes integration test starting |
|
Jenkins retest this please |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Jenkins retest this please |
|
Test build #136468 has started for PR 30679 at commit |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Jenkins retest this please |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #136574 has finished for PR 30679 at commit
|
|
Merged to master |
What changes were proposed in this pull request?
Deprecating
spark.launcher.childConectionTimeoutin favor ofspark.launcher.childConnectionTimeoutWhy are the changes needed?
@srowen suggested it #30323 (comment)
How was this patch tested?
No testing. Not even compiled