[
https://issues.apache.org/jira/browse/YARN-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568825#comment-16568825
]
Eric Yang commented on YARN-8523:
---------------------------------
{quote}
But how would that be done? Just have it constantly listening? That seems like
a lot of pain and overhead for a use case that is probably rather rare.
{quote}
In node manager, create a rest api that accepts container id, and verifies the
user credential matches the owner of the container id or YARN admin. If
security access is granted, it start a web socket thread for the conversation
until the connection is interrupted or terminated. Java ProcessBuilder and
javax.websocket package make the entire process straight forward and light
weight. I think this is a very useful feature for debugging a running
container without limiting to log viewer for troubleshooting.
{quote}
I suppose it's possible to reconnect if we're using live-restore, but I don't
think that is something that needs to be done in the first phase of this
proposal.
{quote}
I am not betting a lot on live restore at this time. There are reports of
docker exec doesn't work after live restore:
https://github.com/moby/moby/issues/35873 . Time will tell if this can be
improved.
> 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]