[
https://issues.apache.org/jira/browse/YARN-9561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923766#comment-16923766
]
Eric Badger commented on YARN-9561:
-----------------------------------
bq. Eric Badger thank you for the debugging session today. I got mapreduce pi
to run correctly after adding /etc/krb5.conf to default mount location.
Fantastic news!! Really great that you were able to get it working end-to-end.
Now we just need to clean the patches up and we should be good to go.
bq. Print a line of output before calling runc. Prelaunch initialization is
completed or print the formatted json in prelaunch.out. This helps to narrow
down the root of the problem is caused by user job configuration or bugs in
container-executor code. Docker runtime shows the command line for calling
docker. This helps to troubleshoot the actual problem sooner.
There's currently a debug line at the end of
{{RuncContainerRuntime.launchContainer()}} that will get printed to the
nodemanager that has the entire JSON that was used to launch the
container-executor. I didn't want to print this to info since the JSON is very
large and scary looking. What do you think?
bq. YARN Docker integration have a list of configurable properties. These
settings do not work with runc container today. Without hinder progress, I
suggest to open new issues to improve integration.
I'm confused as to what you're asking here. In [this
comment|https://issues.apache.org/jira/browse/YARN-9560?focusedCommentId=16851429&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16851429]
on YARN-9560 you didn't want the configs to be mapped together. Now it sounds
like you want there to be integration. Could you clarify this for me?
bq. YARN service uses the properties defined in #3 for customize YARN services
mount points, network to use, and privilege container flag. Similar feature
sets need new tickets to ensure the new runtime can integrate well with YARN
service programming interfaces.
Yes, absolutely. As we talked on the docker meeting call, there are a lot of
things that will need to be added onto the runC runtime so that it can do the
same things that Docker does, and followup JIRAs are a good place for those. If
you have specific suggestions on things that you would like to be added, feel
free to create JIRAs. Otherwise I'll create a list at some point.
> Add C changes for the new RuncContainerRuntime
> ----------------------------------------------
>
> Key: YARN-9561
> URL: https://issues.apache.org/jira/browse/YARN-9561
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Badger
> Assignee: Eric Badger
> Priority: Major
> Attachments: YARN-9561.001.patch, YARN-9561.002.patch,
> YARN-9561.003.patch, YARN-9561.004.patch
>
>
> This JIRA will be used to add the C changes to the container-executor native
> binary that are necessary for the new RuncContainerRuntime. There should be
> no changes to existing code paths.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
