[ https://issues.apache.org/jira/browse/APEXCORE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085875#comment-16085875 ]
Priyanka Gugale commented on APEXCORE-602: ------------------------------------------ Testing covered: 1. Wrote unit tests 2. Simulated operator failure recursively where before redeploy on a operator is finished it fails again. This creates multiple deploy request in parallel for a operator but different containers. (Forced to throw exception on certain conditions). 3. Manually killed a operator and predecessor operator within very short duration to make same operators redeploy in multiple requests. 4. Random killing of operator/containers for testing. > Provide a "group-id" in the event object so that events are grouped together > by a "root cause". > ----------------------------------------------------------------------------------------------- > > Key: APEXCORE-602 > URL: https://issues.apache.org/jira/browse/APEXCORE-602 > Project: Apache Apex Core > Issue Type: Improvement > Reporter: Sanjay M Pujare > Assignee: Priyanka Gugale > Fix For: 3.7.0 > > > Provide a "group-id" in the event object so that events are grouped together > by a "root cause". An example is a bunch of container restarts are related to > a single failure in the application but the current sequence of Stram events > doesn't make it obvious. The consumer of events is able to better > read/analyze the events because of the group-id and focus on the root-cause. -- This message was sent by Atlassian JIRA (v6.4.14#64029)