Skip to content
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

[SPARK-51061][CORE] Hide Jetty info in REST Submission API #49762

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dongjoon-hyun
Copy link
Member

@dongjoon-hyun dongjoon-hyun commented Feb 2, 2025

What changes were proposed in this pull request?

This PR aims to hide Jetty info in REST Submission API like SPARK-46239.

Why are the changes needed?

Start Spark Master server.

$ SPARK_MASTER_OPTS='-Dspark.master.rest.enabled=true' sbin/start-master.sh

BEFORE:

$ curl -vv http://0.0.0.0:6066/v1/submissions/readyz
*   Trying 0.0.0.0:6066...
* Connected to 0.0.0.0 (0.0.0.0) port 6066
> GET /v1/submissions/readyz HTTP/1.1
> Host: 0.0.0.0:6066
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Date: Sun, 02 Feb 2025 05:14:04 GMT
< Content-Type: application/json;charset=utf-8
< Content-Length: 114
< Server: Jetty(11.0.24)
<
{
  "action" : "ReadyzResponse",
  "message" : "",
  "serverSparkVersion" : "4.1.0-SNAPSHOT",
  "success" : true
* Connection #0 to host 0.0.0.0 left intact
}

AFTER

$ curl -vv http://0.0.0.0:6066/v1/submissions/readyz
*   Trying 0.0.0.0:6066...
* Connected to 0.0.0.0 (0.0.0.0) port 6066
> GET /v1/submissions/readyz HTTP/1.1
> Host: 0.0.0.0:6066
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Date: Sun, 02 Feb 2025 05:12:41 GMT
< Content-Type: application/json;charset=utf-8
< Content-Length: 114
<
{
  "action" : "ReadyzResponse",
  "message" : "",
  "serverSparkVersion" : "4.1.0-SNAPSHOT",
  "success" : true
* Connection #0 to host 0.0.0.0 left intact
}

Does this PR introduce any user-facing change?

No, there is no technical behavior change because this is a meta-data.

How was this patch tested?

Manual test with the above procedure.

Was this patch authored or co-authored using generative AI tooling?

No.

@github-actions github-actions bot added the CORE label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant