Unpin Dataflow legacy worker container for Nexmark test

[Abacn]

fix #30606

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @kennknowles for label java.
R: @damccorm for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[damccorm]

Instead of doing this, should we be fixing #30606 (comment) so that it points to a java 11 container?

[Abacn]

Instead of doing this, should we be fixing #30606 (comment) so that it points to a java 11 container?

This PR is to fix that comment. The effect of '--workerHarnessContainerImage=' is to direct the container to an internally built (Java 8) container, which made it incompatible with pipeline submission environment. Remove it, it will use beam-master container with the same Java version of the host, while still overrides dataflowWorkerJar

[damccorm]

My question was: should we make --workerHarnessContainerImage= cause Dataflow to point to a Java 11 container? I think there might still be some advantages to doing this per #6694 (comment)

[Abacn]

I see, yeah, we should move the internal one to java11, will raise internal tracker for that

[Abacn]

Opened an internal issue (tracking: 381121973) and initial changes. It seems the scope of change for migrating the staging container to Java11 is nontrivial, and needs rollouts from Dataflow service side (which is currently blocked). Could we proceed with this change for this workflow at the moment?

[damccorm]

Opened an internal issue (tracking: 381121973) and initial changes. It seems the scope of change for migrating the staging container to Java11 is nontrivial, and needs rollouts from Dataflow service side (which is currently blocked). Could we proceed with this change for this workflow at the moment?

Yeah, that is fine - thanks