Re: [DISCUSS] Stram events log levels
Nice point Tushar. I will look into how we can pass on different event log
levels for same event type.
Ajay
On Fri, Jan 20, 2017 at 10:18 AM, Tushar Gosavi
wrote:
> +1 for this feature. The event priority is not statically defained by
> its type, it also depends on on context in which event is generated.
> for example STOP_CONTAINER event could be because of
>
> - jvm issue/out of memory - This could be at much higher level
> - All operators in containers have shutdown voluntary/or extra
> container released - this could be at lower level.
>
> - Tushar.
>
>
>
> On Fri, Jan 20, 2017 at 12:32 AM, Sanjay Pujare
> wrote:
> > Strong +1 for the reasons cited by Ajay and Hitesh.
> >
> > Do we really need to modify the EventInfo class? Wouldn’t the
> BeanUtils.describe(event) automatically populate the EventLogLevel into
> “data” (a Map) as a property? All the downstream code
> including the REST API will then just return the EventLogLevel as part of
> JSONObject without making any changes, right?
> >
> > Another thing: these levels should ideally match the corresponding
> entries in the dt.log file as some users might expect.
> >
> > On 1/19/17, 10:10 AM, "Hitesh Kapoor" wrote:
> >
> > +1 it will enhance the user experience and the approach suggested by
> Ajay
> > doesn't seems to add significant overhead. Also I feel that in
> future it
> > can be enhanced further and UI can also filter the event logs based
> on
> > these log levels.
> >
> > On Jan 19, 2017 10:57 PM, "AJAY GUPTA" wrote:
> >
> > > Current event log mechanism : The events recorded are currently
> recorded in
> > > datatorrent/apps/{appid}/events/folder in files named
> part{id}.txt .
> > > eg
> > > : datatorrent/apps/application_1483801541352_0003/events/part0.txt
> > >
> > > We can access these events via REST Api which returns the list of
> events as
> > > List objects.
> > >
> > >
> > > The below approach can be used for implementing this. Kindly let
> me know
> > > your viewpoints/suggestions on the approach.
> > >
> > > *Required Changes:*
> > >
> > > a) Add a enum field like EventLogLevel in StramEvent, assign the
> log level
> > > in constructors of different Stram events like StartOperator,
> > > StartContainer, StopOperator, etc.
> > >
> > > b) Add eventLogLevel in EventInfo class. The events returned via
> REST api
> > > from StramClient is a list of EventInfo objects.
> > >
> > > c) Changes in EventsAgent - processPartFile() method to parse the
> > > eventLogLevel logged into the part{id}.txt file
> > >
> > >
> > > On Thu, Jan 19, 2017 at 10:55 PM, AJAY GUPTA
> wrote:
> > >
> > > > Hi Apex community,
> > > >
> > > >
> > > > Currently, events logged by stram such as StartContainer,
> StartOperator,
> > > > StopContainer, StopOperator, etc dont have any associated
> priority level.
> > > >
> > > > We can provide log levels for such Stram events. Log levels can
> be INFO,
> > > > WARN, ERROR
> > > > Eg:
> > > > 1. Start Container, Start Operator are INFO level events
> > > > 2. OperatorError is ERROR level event
> > > > 3. Stop Container, Stop Operator are WARN level events
> > > >
> > > > Log level for events can help in user experience when showing
> the event
> > > > list in a GUI. eg: In datatorrent gateway UI, we can provide
> color-coded
> > > > log levels so that user can focus more on ERROR and WARN events.
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
>
Packaging apex app using maven-shade plugin.
Hello Everyone, I have tried and successfully packaged apex app using maven shade plugin. 1. Remove the maven-assembly plugin and replace it with the following shade plugin. org.apache.maven.plugins maven-shade-plugin 2.4.3 true bin *:* META-INF/*.SF META-INF/*.DSA META-INF/*.RSA package shade META-INF/* 2. Replace the target in maven-antrun plugin with this : 3. Uncomment the following from the default pom.xml to exlude transitive dependencies. * * Here is the complete pom.xml https://gist.github.com/ambarishpande/45f98b40d3640fa9b1f5c6a1f0167a27 Hope it helps someone in need. Thank you.
[GitHub] apex-core pull request #449: Set right margin to 120. Do not wrap long lines...
GitHub user vrozov opened a pull request: https://github.com/apache/apex-core/pull/449 Set right margin to 120. Do not wrap long lines. @davidyan74 Please merge You can merge this pull request into a Git repository by running: $ git pull https://github.com/vrozov/apex-core codeStyleSettings Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/449.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #449 commit 76f55a826369d93e69617a18b6cb8babb1667305 Author: Apex Dev Date: 2017-01-20T15:13:36Z Set right margin to 120. Do not wrap long lines. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: APEXCORE-294 Clean application shutdown
As discussed please also look at appropriate user documentation and clarity WRT the CLI commands. Thanks, Thomas On Thu, Jan 19, 2017 at 10:46 PM, Tushar Gosavi wrote: > Hi Thomas, > > As discussed I will remote the old behaviour of shutdown. > > - Tushar. > > On Fri, Jan 20, 2017 at 10:03 AM, Tushar Gosavi > wrote: > > Hi Thomas, > > > > I agree with you on the current behavior. The effect of shutdown can > > be achieve with kill. I was more worried about backward compatibility > > issue > > while relaunching the shutdown app, hence kept the default as same as > > before (cli and rest api default). If we don't want to retain the > > relaunch > > behaviour of shutdown app then the code will be more simpler :). Let > > me know, I will update the PR accordinlgy. > > > > - Tushar. > > > > > > On Thu, Jan 19, 2017 at 9:22 PM, Thomas Weise wrote: > >> Tushar, > >> > >> I would like to see the use case for "hard shutdown" vs kill. The > current > >> shutdown behavior isn't useful, confusing and sometimes does not even > end > >> the app (based on feedback received in the past from users). I would > prefer > >> we don't retain it without clear understanding of use case and how it > will > >> really work. > >> > >> Thanks, > >> Thomas > >> > >> > >> On Wed, Jan 18, 2017 at 1:41 AM, Tushar Gosavi > >> wrote: > >> > >>> Dear Community, > >>> > >>> I have changed the implementaion plan based on PR comments. Following > >>> is the new proposal for this feature. > >>> > >>> https://docs.google.com/a/datatorrent.com/document/d/ > 1hSLH4xi_15OWwW4KY7-- > >>> LU3e2iHHhfthOpATicnC5eE/edit?usp=sharing > >>> > >>> Please provide the feedback. I will update the PR accrodinly. > >>> > >>> - Tushar. > >>> > >>> > >>> On Fri, Nov 25, 2016 at 4:40 PM, Tushar Gosavi > > >>> wrote: > >>> > Dear Community, > >>> > > >>> > I have open an pull request for shutting down application by sending > >>> > END_STREAM control tuples from all input operator. This is similar to > >>> > all input operator have stopped after raising ShutdownException. > >>> > > >>> > On receiving shutdown request, master will prepare OPERATOR_STOP > >>> > command for all input partitions, and send it to container as part of > >>> > heartbeat response to container. Container will shutdown the operator > >>> > thread after receiving this command. > >>> > > >>> > https://github.com/apache/apex-core/pull/424 > >>> > Please review. > >>> > > >>> > Thanks, > >>> > - Tushar. > >>> >
Re: Upgrade Apache Bigtop to Apex Core 3.5.0
+1 Thks Amol On Thu, Jan 19, 2017 at 8:55 PM, Priyanka Gugale wrote: > +1 > > On Fri, Jan 20, 2017 at 9:25 AM, Chinmay Kolhatkar < > chin...@datatorrent.com> > wrote: > > > Sanjay, > > Its not a lot of work. Just a version change, but primarily follwing > apache > > process for bigtop. > > Powered by Page of bigtop is here: > > https://cwiki.apache.org/confluence/display/BIGTOP/Powered+By+Bigtop > > Looking at the existing content, I would like to know what we can add > > there. > > > > All, > > Thanks for feedback. I'll start communication on bigtop mailing list for > > version upgrade. > > > > > > > > On Fri, Jan 20, 2017 at 12:09 AM, Sanjay Pujare > > wrote: > > > > > +1 assuming not a lot of work is involved. > > > > > > What does it take to add a mention of Apex in > http://bigtop.apache.org/ > > ? > > > > > > On 1/19/17, 8:12 AM, "Pramod Immaneni" wrote: > > > > > > +1 > > > > > > On Thu, Jan 19, 2017 at 12:53 AM, Chinmay Kolhatkar < > > > chin...@datatorrent.com > > > > wrote: > > > > > > > Dear Community, > > > > > > > > Now that Apex core 3.5.0 is released, is it good time to upgrade > > > Apache > > > > Bigtop for Apex to 3.5.0? > > > > > > > > -Chinmay. > > > > > > > > > > > > > > > > > > >
[jira] [Created] (APEXCORE-616) Application fails to launch on Kerberised cluster
Venkatesh Kottapalli created APEXCORE-616: - Summary: Application fails to launch on Kerberised cluster Key: APEXCORE-616 URL: https://issues.apache.org/jira/browse/APEXCORE-616 Project: Apache Apex Core Issue Type: Bug Affects Versions: 3.5.0 Environment: CDH - any Reporter: Venkatesh Kottapalli Application fails to start in a Kerberised cluster with the following exception. 2017-01-20 19:28:07,408 [main] ERROR stram.StreamingAppMaster main - Exiting Application Master java.lang.NoClassDefFoundError: com/sun/jersey/client/apache4/ApacheHttpClient4Handler at com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:153) at com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:140) at com.datatorrent.stram.StreamingContainerManager.getAppMasterContainerInfo(StreamingContainerManager.java:481) at com.datatorrent.stram.StreamingContainerManager.init(StreamingContainerManager.java:448) at com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:420) at com.datatorrent.stram.StreamingContainerManager.getInstance(StreamingContainerManager.java:3065) at com.datatorrent.stram.StreamingAppMasterService.serviceInit(StreamingAppMasterService.java:552) at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at com.datatorrent.stram.StreamingAppMaster.main(StreamingAppMaster.java:102) Caused by: java.lang.ClassNotFoundException: com.sun.jersey.client.apache4.ApacheHttpClient4Handler at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 9 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (APEXCORE-616) Application fails to launch on Kerberised cluster
[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pramod Immaneni reassigned APEXCORE-616: Assignee: Pramod Immaneni > Application fails to launch on Kerberised cluster > - > > Key: APEXCORE-616 > URL: https://issues.apache.org/jira/browse/APEXCORE-616 > Project: Apache Apex Core > Issue Type: Bug >Affects Versions: 3.5.0 > Environment: CDH - any >Reporter: Venkatesh Kottapalli >Assignee: Pramod Immaneni > > Application fails to start in a Kerberised cluster with the following > exception. > 2017-01-20 19:28:07,408 [main] ERROR stram.StreamingAppMaster main - Exiting > Application Master > java.lang.NoClassDefFoundError: > com/sun/jersey/client/apache4/ApacheHttpClient4Handler > at > com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:153) > at > com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:140) > at > com.datatorrent.stram.StreamingContainerManager.getAppMasterContainerInfo(StreamingContainerManager.java:481) > at > com.datatorrent.stram.StreamingContainerManager.init(StreamingContainerManager.java:448) > at > com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:420) > at > com.datatorrent.stram.StreamingContainerManager.getInstance(StreamingContainerManager.java:3065) > at > com.datatorrent.stram.StreamingAppMasterService.serviceInit(StreamingAppMasterService.java:552) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > com.datatorrent.stram.StreamingAppMaster.main(StreamingAppMaster.java:102) > Caused by: java.lang.ClassNotFoundException: > com.sun.jersey.client.apache4.ApacheHttpClient4Handler > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 9 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (APEXCORE-616) Application fails to start Kerberised cluster
[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Kottapalli updated APEXCORE-616: -- Summary: Application fails to start Kerberised cluster (was: Application fails to launch on Kerberised cluster) > Application fails to start Kerberised cluster > - > > Key: APEXCORE-616 > URL: https://issues.apache.org/jira/browse/APEXCORE-616 > Project: Apache Apex Core > Issue Type: Bug >Affects Versions: 3.5.0 > Environment: CDH - any >Reporter: Venkatesh Kottapalli >Assignee: Pramod Immaneni > > Application fails to start in a Kerberised cluster with the following > exception. > 2017-01-20 19:28:07,408 [main] ERROR stram.StreamingAppMaster main - Exiting > Application Master > java.lang.NoClassDefFoundError: > com/sun/jersey/client/apache4/ApacheHttpClient4Handler > at > com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:153) > at > com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:140) > at > com.datatorrent.stram.StreamingContainerManager.getAppMasterContainerInfo(StreamingContainerManager.java:481) > at > com.datatorrent.stram.StreamingContainerManager.init(StreamingContainerManager.java:448) > at > com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:420) > at > com.datatorrent.stram.StreamingContainerManager.getInstance(StreamingContainerManager.java:3065) > at > com.datatorrent.stram.StreamingAppMasterService.serviceInit(StreamingAppMasterService.java:552) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > com.datatorrent.stram.StreamingAppMaster.main(StreamingAppMaster.java:102) > Caused by: java.lang.ClassNotFoundException: > com.sun.jersey.client.apache4.ApacheHttpClient4Handler > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 9 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] apex-core pull request #450: APEXCORE-616 Added back http client handler tha...
GitHub user PramodSSImmaneni opened a pull request: https://github.com/apache/apex-core/pull/450 APEXCORE-616 Added back http client handler that was removed and affects running in kerberized cluster @venkateshkottapalli @davidyan74 please see You can merge this pull request into a Git repository by running: $ git pull https://github.com/PramodSSImmaneni/apex-core APEXCORE-616 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/450.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #450 commit 0596d9606ba5e104b54d6936bfc76f3c040f6fae Author: Pramod Immaneni Date: 2017-01-21T02:07:27Z APEXCORE-616 Added back http client handler library which bridges http client and jersey for accessing kerberized web services that was removed earlier when upgrading to Hadoop 2.6 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (APEXCORE-616) Application fails to start Kerberised cluster
[ https://issues.apache.org/jira/browse/APEXCORE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832739#comment-15832739 ] ASF GitHub Bot commented on APEXCORE-616: - GitHub user PramodSSImmaneni opened a pull request: https://github.com/apache/apex-core/pull/450 APEXCORE-616 Added back http client handler that was removed and affects running in kerberized cluster @venkateshkottapalli @davidyan74 please see You can merge this pull request into a Git repository by running: $ git pull https://github.com/PramodSSImmaneni/apex-core APEXCORE-616 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/450.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #450 commit 0596d9606ba5e104b54d6936bfc76f3c040f6fae Author: Pramod Immaneni Date: 2017-01-21T02:07:27Z APEXCORE-616 Added back http client handler library which bridges http client and jersey for accessing kerberized web services that was removed earlier when upgrading to Hadoop 2.6 > Application fails to start Kerberised cluster > - > > Key: APEXCORE-616 > URL: https://issues.apache.org/jira/browse/APEXCORE-616 > Project: Apache Apex Core > Issue Type: Bug >Affects Versions: 3.5.0 > Environment: CDH - any >Reporter: Venkatesh Kottapalli >Assignee: Pramod Immaneni > > Application fails to start in a Kerberised cluster with the following > exception. > 2017-01-20 19:28:07,408 [main] ERROR stram.StreamingAppMaster main - Exiting > Application Master > java.lang.NoClassDefFoundError: > com/sun/jersey/client/apache4/ApacheHttpClient4Handler > at > com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:153) > at > com.datatorrent.stram.util.WebServicesClient.(WebServicesClient.java:140) > at > com.datatorrent.stram.StreamingContainerManager.getAppMasterContainerInfo(StreamingContainerManager.java:481) > at > com.datatorrent.stram.StreamingContainerManager.init(StreamingContainerManager.java:448) > at > com.datatorrent.stram.StreamingContainerManager.(StreamingContainerManager.java:420) > at > com.datatorrent.stram.StreamingContainerManager.getInstance(StreamingContainerManager.java:3065) > at > com.datatorrent.stram.StreamingAppMasterService.serviceInit(StreamingAppMasterService.java:552) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > com.datatorrent.stram.StreamingAppMaster.main(StreamingAppMaster.java:102) > Caused by: java.lang.ClassNotFoundException: > com.sun.jersey.client.apache4.ApacheHttpClient4Handler > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 9 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (APEXCORE-596) Committed method on operators not called when stream locality is THREAD_LOCAL
[
https://issues.apache.org/jira/browse/APEXCORE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832748#comment-15832748
]
ASF GitHub Bot commented on APEXCORE-596:
-
Github user asfgit closed the pull request at:
https://github.com/apache/apex-core/pull/442
> Committed method on operators not called when stream locality is THREAD_LOCAL
> -
>
> Key: APEXCORE-596
> URL: https://issues.apache.org/jira/browse/APEXCORE-596
> Project: Apache Apex Core
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Francis Fernandes
>Assignee: Francis Fernandes
>
> When the locality of the stream connecting the two operators is
> Locality.THREAD_LOCAL, the committed method is not called for some operators.
> These operators implement the Operator.CheckpointListener. e.g.
> AbstractFileOutputOperator
> For thread local during activate we do not set the thread in the node's
> context
> Because the thread is not set, we skip this operator in the
> processHeartBeatResponse and the committed is not called
> {code}
> if (thread == null || !thread.isAlive()) {
> continue;
> }
> {code}
> We need this condition for invalid operators (operator failures) in case of
> other localities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] apex-core pull request #442: APEXCORE-596 Setting the thread for all oio nod...
Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/442 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (APEXCORE-596) Committed method on operators not called when stream locality is THREAD_LOCAL
[
https://issues.apache.org/jira/browse/APEXCORE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov resolved APEXCORE-596.
-
Resolution: Fixed
Fix Version/s: 3.6.0
> Committed method on operators not called when stream locality is THREAD_LOCAL
> -
>
> Key: APEXCORE-596
> URL: https://issues.apache.org/jira/browse/APEXCORE-596
> Project: Apache Apex Core
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Francis Fernandes
>Assignee: Francis Fernandes
>Priority: Minor
> Fix For: 3.6.0
>
>
> When the locality of the stream connecting the two operators is
> Locality.THREAD_LOCAL, the committed method is not called for some operators.
> These operators implement the Operator.CheckpointListener. e.g.
> AbstractFileOutputOperator
> For thread local during activate we do not set the thread in the node's
> context
> Because the thread is not set, we skip this operator in the
> processHeartBeatResponse and the committed is not called
> {code}
> if (thread == null || !thread.isAlive()) {
> continue;
> }
> {code}
> We need this condition for invalid operators (operator failures) in case of
> other localities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (APEXCORE-596) Committed method on operators not called when stream locality is THREAD_LOCAL
[
https://issues.apache.org/jira/browse/APEXCORE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Rozov updated APEXCORE-596:
Priority: Minor (was: Major)
> Committed method on operators not called when stream locality is THREAD_LOCAL
> -
>
> Key: APEXCORE-596
> URL: https://issues.apache.org/jira/browse/APEXCORE-596
> Project: Apache Apex Core
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Francis Fernandes
>Assignee: Francis Fernandes
>Priority: Minor
> Fix For: 3.6.0
>
>
> When the locality of the stream connecting the two operators is
> Locality.THREAD_LOCAL, the committed method is not called for some operators.
> These operators implement the Operator.CheckpointListener. e.g.
> AbstractFileOutputOperator
> For thread local during activate we do not set the thread in the node's
> context
> Because the thread is not set, we skip this operator in the
> processHeartBeatResponse and the committed is not called
> {code}
> if (thread == null || !thread.isAlive()) {
> continue;
> }
> {code}
> We need this condition for invalid operators (operator failures) in case of
> other localities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
