[
https://issues.apache.org/jira/browse/TEZ-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677445#comment-15677445
]
Ming Ma commented on TEZ-3222:
------------------------------
[~jeagles], the fair routing part looks good. Couple questions:
* This includes EdgeManagerPluginOnDemand API, Is there any 3rd party plugin
that depends on the old signature?
* CompositeRoutedDataMovementEvent has comment {{Event used by user code to
send information between tasks.}}. How is that used by user node? It seems the
relevant part is EdgeManagerPlugin provider, which needs to return
CompositeEventRouteMetadata.
* Should routeInputSourceTaskFailedEventToDestination be optimized as well?
* What if routeCompositeDataMovementEventToDestination returns null
CompositeEventRouteMetadata?
Given CompositeRoutedDataMovementEvent adds target indices compared to
CompositeRoutedDataMovementEvent, will it help if using inheritance?
* Maybe the following block in ShuffleInputEventHandlerImpl and
ShuffleInputEventHandlerOrderedGrouped can be moved to a common function used
by all cases?
{noformat}
if (shufflePayload.hasEmptyPartitions()) {
...
}
{noformat}
> Reduce messaging overhead for auto-reduce parallelism case
> ----------------------------------------------------------
>
> Key: TEZ-3222
> URL: https://issues.apache.org/jira/browse/TEZ-3222
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-3222.1.patch, TEZ-3222.2.patch, TEZ-3222.3.patch,
> TEZ-3222.4.patch, TEZ-3222.5.patch, TEZ-3222.6.patch, TEZ-3222.7.patch
>
>
> A dag with 15k x 1000k vertex may auto-reduce to 15k x 1. And while the data
> size is appropriate for 1 task attempt, this results in an increase in task
> attempt message processing of 1000x.
> This jira aims to reduce the message processing in the auto-reduced task
> while keeping the amount of message processing in the AM the same or less.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
