[
https://issues.apache.org/jira/browse/TEZ-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574538#comment-17574538
]
László Bodor commented on TEZ-4236:
-----------------------------------
not needed, can still can be used, I mean tez.local.mode is very good for
testing as it eliminates lots of complexity, but still makes sense to use the
RPC communication, let's say when we intentionally want to verify the RPC
interface itself...however, we can consider setting this true as default in the
future
> DAGClientServer is not really needed to be started/used in local mode
> ---------------------------------------------------------------------
>
> Key: TEZ-4236
> URL: https://issues.apache.org/jira/browse/TEZ-4236
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Fix For: 0.10.1
>
> Attachments: TEZ-4236.01.patch, TEZ-4236.02.patch, TEZ-4236.03.patch,
> TEZ-4236.04.patch, TEZ-4236.05.patch, TEZ-4236.06.patch
>
>
> For a customer, we found that they try to run hive on tez local mode tests,
> and due to strict firewall rules and security policy, the DagClientServer
> struggles to start or respond to connections (think about corporate laptops
> here). Instead of investigating the network-related workarounds, let's find
> another way and decide if DAGAppMaster really needs this server.
> LocalClient has an embedded
> [DAGAppMaster|https://github.com/apache/tez/blob/master/tez-dag/src/main/java/org/apache/tez/client/LocalClient.java#L65],
> so at the first sight, it doesn't make sense to rely on the network
> environment in terms of AM usage. Hopefully, AM can become more lightweight
> in the long term if we try to eliminate pointless network usage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
