ASF GitHub Bot commented on APEXCORE-474:

GitHub user sandeshh opened a pull request:


    [WIP] APEXCORE-474 In M*1 case, deploy the unifier in the same container as…

    … downstream
    Opening this, work in progress, PR to get early feedback. Only changes I am 
doing is for unit tests.
    There are another 4 failing tests.
    @tweise and @PramodSSImmaneni Please review.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sandeshh/apex-core APEXCORE-474

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #395
commit 91a8470b7e465ba767372956d3311238d720c23e
Author: sandeshh <sandesh.he...@gmail.com>
Date:   2016-09-20T22:56:23Z

    APEXCORE-474 In M*1 case, deploy the unifier in the same container as 


> Unifier placement during M*1 deployment
> ---------------------------------------
>                 Key: APEXCORE-474
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-474
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Sandesh
>            Assignee: Sandesh
> During M*1 deployment, unifier was deployed in the separate container. But 
> there is no advantage in doing that. 
> It is better to make the unifier THREAD_LOCAL with the downstream operator.
> ( https://issues.apache.org/jira/browse/APEXCORE-482 )
> Note:
> Recently saw one Kafka ETL app, that had a total of 18 containers allocated, 
> but out of that 5 containers were allocated for default unifiers. It also 
> means, lots of time is spent in SerDe. 
> Implementing this feature will improve the performance greatly.

This message was sent by Atlassian JIRA

Reply via email to