[SPARK-36834][SHUFFLE] Add support for namespacing log lines emitted by external shuffle service#34079
[SPARK-36834][SHUFFLE] Add support for namespacing log lines emitted by external shuffle service#34079thejdeep wants to merge 1 commit into
Conversation
|
+CC @tgravescs, @Ngone51 |
c85599f to
59cdb03
Compare
|
conceptually looks fine to me too. |
c13c3a2 to
d0380ec
Compare
d432baa to
6c754cf
Compare
|
@tgravescs @mridulm @xkrogen Addressed the comments, please review. Thanks |
xkrogen
left a comment
There was a problem hiding this comment.
Logic itself LGTM, I think having the base static logger which we later override is a good approach
I think we can make the documentation/messages a bit more user friendly
xkrogen
left a comment
There was a problem hiding this comment.
LGTM except for minor formatting comment
|
@mridulm @tgravescs Please take a look, thanks! |
mridulm
left a comment
There was a problem hiding this comment.
+CC @tgravescs, @xkrogen
|
Ok to test |
|
Test build #144271 has finished for PR 34079 at commit
|
|
Kubernetes integration test starting |
…by ESS ### What changes were proposed in this pull request? Added a config `spark.yarn.shuffle.service.logs.namespace` which can be used to add a namespace suffix to log lines emitted by the External Shuffle Service. ### Why are the changes needed? Since many instances of ESS can be running on the same NM, it would be easier to distinguish between them. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? N/A
|
Test build #144272 has finished for PR 34079 at commit
|
|
Kubernetes integration test status failure |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
What changes were proposed in this pull request?
Added a config
spark.yarn.shuffle.service.logs.namespacewhich can be used to add a namespace suffix to log lines emitted by the External Shuffle Service.Why are the changes needed?
Since many instances of ESS can be running on the same NM, it would be easier to distinguish between them.
Does this PR introduce any user-facing change?
No
How was this patch tested?
N/A