[
https://issues.apache.org/jira/browse/YARN-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574174#comment-16574174
]
Eric Yang commented on YARN-8523:
---------------------------------
[~Zian Chen] In today's meetup, [~jlowe] suggested to bind docker exec to a
named pipe or socket. This will allow node manager restart while persisting
docker exec state, and reconnect to the named pipe to resume docker exec
session. This is one approach to workaround node manager restart while
maintains a live session to docker exec. However, resuming docker exec session
may introduce limitation where docker exec is stuck, and no way to start new
sessions. Step one is get xtermjs connect to web socket serve by node manager
that launches docker exec. Step 2 can refine the session mapping logic to
create/resume named pipe to docker exec. I think it would be reasonable for
step 2 to be created as a separate JIRA to contain the scope of the work.
> Interactive docker shell
> ------------------------
>
> Key: YARN-8523
> URL: https://issues.apache.org/jira/browse/YARN-8523
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Eric Yang
> Priority: Major
> Labels: Docker
>
> Some application might require interactive unix commands executions to carry
> out operations. Container-executor can interface with docker exec to debug
> or analyze docker containers while the application is running. It would be
> nice to support an API to invoke docker exec to perform unix commands and
> report back the output to application master. Application master can
> distribute and aggregate execution of the commands to record in application
> master log file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
