[ 
https://issues.apache.org/jira/browse/HADOOP-18913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Szucs updated HADOOP-18913:
---------------------------------
    Description: 
There was a previous ticket for adding add-opens flag to container launch to be 
able to run them on JDK17 nodes: 
https://issues.apache.org/jira/browse/MAPREDUCE-7449

As testing discovered, this should be extended with 
"{_}-add-exports=java.base/sun.net.dns=ALL-UNNAMED{_}" and 
"{_}-add-exports=java.base/sun.net.util=ALL-UNNAMED{_}" options to be able to 
run containers on Isilon.

  was:
There was a previous ticket for adding add-opens flag to container launch to be 
able to run them on JDK17 nodes: 
https://issues.apache.org/jira/browse/MAPREDUCE-7449

As testing discovered, this should be extended with 
"{_}--add-exports=java.base/sun.net.dns=ALL-UNNAMED{_}" and 
"{_}--add-exports=java.base/sun.net.util=ALL-UNNAMED{_}" options to be able to 
run containers on Isilon.


> Extend add-opens flag to container launch commands on JDK17 nodes
> -----------------------------------------------------------------
>
>                 Key: HADOOP-18913
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18913
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 3.4.0
>            Reporter: Peter Szucs
>            Assignee: Peter Szucs
>            Priority: Major
>
> There was a previous ticket for adding add-opens flag to container launch to 
> be able to run them on JDK17 nodes: 
> https://issues.apache.org/jira/browse/MAPREDUCE-7449
> As testing discovered, this should be extended with 
> "{_}-add-exports=java.base/sun.net.dns=ALL-UNNAMED{_}" and 
> "{_}-add-exports=java.base/sun.net.util=ALL-UNNAMED{_}" options to be able to 
> run containers on Isilon.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to