apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DT-Priyanka <...@git.apache.org>
Subject [GitHub] apex-core pull request #479: [Review only] APEXCORE-602: group events by cau...
Date Fri, 24 Feb 2017 13:00:06 GMT
GitHub user DT-Priyanka opened a pull request:


    [Review only] APEXCORE-602: group events by cause

    This feature is to group events which are raised due to common cause e.g. if a operator
fails it causes all downstream operators to redeploy and this action raises bunch of events.
The events should have common groupId for reference.
    The code changes following following path for code changes:
    **When Operator throws an exception,**
    1. StreamingContainer containing operator generates a event groupId and raises OperatorErrorEvent
with generated groupId
    2. Then StreamingContainer sends groupId to StrAM in heartbeat
    3. StaAM saves this groupId for future use.
    4. When StreamingAppMasterService detects that a container is killed with non-zero exit
code it schedules redeployment for all downstream operators.
    5. StrAM, when scheduling redeployment for downstream operators maps groupId to all scheduled
    6. StrAM then sends undeploy signals to operators along with groupId in heartbeat response.
StrAM also raises OperatorStop event and refers to same groupId.
    7.  StreamingContainer remember groupId and sends it back in heartbeat when it starts
operator again.
    8. StrAM then uses this groupId to raise OperatorStart event.
    StrAM also tracks container stop and start to raise ContainerStop and ContainerStart events.
    **When StrAM kills a container**
    1. StreamingAppMasterService detects that a container is killed and removes container
agent. As well as creates RedeploymentInformation with groupId
    2.  follows steps 4-8 from above flow

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

    $ git pull https://github.com/DT-Priyanka/incubator-apex-core APEXCORE-602-events-grouping

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 #479
commit ae8a6ab3ad3107627eb6bea886b4e167fa669d3b
Author: priya <priyag@apache.org>
Date:   2017-02-23T11:55:56Z

    APEXCORE-602: group events by cause


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message