Re: Nifi Issue

[Joe Skora]

Ramesh,

Without more information, it's hard to help troubleshoot your problems.

   - Are you able to get data into NiFi from Oracle or CSV?
   - If data is getting into NiFi, do the contents look correct?  (You can
   use LogAttribute with Log Payload set.)
   - What are the problems you see putting the files into HDFS?
   - Are there any exceptions in the "nifi-app.log" log file?

Regards
Joe

On Mon, Feb 15, 2016 at 5:03 PM, Veerappan, Ramesh <
ramesh.veerap...@railinc.com> wrote:

> Can you help me line up a resource for Nifi ?   I have tried couple of
> thing over the weekends.  I am not able to move files from Oracle to HDFS
> or even CSV to HDFS.I am available the following times: on Feb 16,
> 2016, Eastern Time Zone
>
> 10 to 11.30
> 2 to 3p.m.
>
>
> 
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail.
>

[GitHub] nifi pull request: Nifi 1516 - AWS DynamoDB Get/Put/Delete Process...

[mans2singh]

GitHub user mans2singh opened a pull request:

https://github.com/apache/nifi/pull/224

Nifi 1516 - AWS DynamoDB Get/Put/Delete Processors

The current implementation supports string and numbers for hash and range 
keys.  For put operations, a json document can be inserted to a specified field 
and for get the the json attribute can be retrieved from the item.

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

$ git pull https://github.com/mans2singh/nifi Nifi-1516

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

https://github.com/apache/nifi/pull/224.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 #224


commit a68f85f0324f2182f6a29dbfec64ffc60ba18422
Author: mans2singh 
Date:   2016-02-15T06:53:52Z

Support for nifi dynamodb get/put/delete

commit e08df1040e606e1f23581f02fe50159a2105f9dc
Author: mans2singh 
Date:   2016-02-15T19:42:51Z

code refactoring and added test cases

commit a8a292e7497211a374106c62f1d08539f301a545
Author: mans2singh 
Date:   2016-02-15T19:47:17Z

contrib related formatting corrections

commit a05d3d08d4fd292f5b0d25959089ee220f7d3f0f
Author: mans2singh 
Date:   2016-02-15T22:37:50Z

code refactoring and tests

commit 1b91025d1f9b246ded50f3f55aa8cdbd59a1a109
Author: mans2singh 
Date:   2016-02-15T22:47:45Z

update test cases

commit 56fc5eeadb49d83dc702bcd27a88de325e115544
Author: mans2singh 
Date:   2016-02-15T23:07:00Z

contrib related error correction

commit d506058f24b737a48f5e7d19258c414e6873385b
Author: mans2singh 
Date:   2016-02-15T23:17:10Z

ignore integration tests




---
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.
---

[GitHub] nifi pull request: Fixed: ExecuteStreamCommand when expressions in...

[michalklempa]

Github user michalklempa commented on the pull request:

https://github.com/apache/nifi/pull/205#issuecomment-184400660
  
Thank you for pointing the right direction.
Here is JIRA https://issues.apache.org/jira/browse/NIFI-1514 issue, new PR: 
https://github.com/apache/nifi/pull/223

You may close this PR as unmerged.


---
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.
---

[ANNOUNCE] New Apache NiFi Committer Joe Skora

[Tony Kurc]

On behalf of the Apache NiFI PMC, I am very pleased to announce that Joe
Skora has accepted the PMC's invitation to become a committer on the Apache
NiFi project. We greatly appreciate all of Joe's hard work and generous
contributions to the project. We look forward to his continued involvement
in the project.

Joe has been involved in the last few releases, to include the coming 0.5.0
release. I certainly had a lot of great exchanges with him as we figured
out where S3 Multipart support should fit into the aws bundle as well as
how to deal with state that is held on someone else's cloud services.

Welcome and congratulations!

Tony Kurc

Re: NCM and node on the same machine?

[Matthew Clarke]

Sai,
You do not need a node on on the same VM running your NCM.  Are you
trying to say that by adding a node on the same machine as your NCM, all
nodes (even those on other VMS) all of a sudden joined?

Question:
Did you populate these fields in your nifi.properties files with IPs or
hostnames (recommended):
   nifi.cluster.node.address=
   nifi.cluster.manager.address=

One of two things is probably happening here:
1. You are using hostnames and your NCM can not resolve those hostnames to
network reachable IP addresses.
2. you left those fields blank the nodes are likely reporting a value of
localhost as their address when they heartbeat to the NCM.  IN this cas
ethe NCM tries talking back to itself which can is why nothing works when
you don't have a Node local.

You should populate all your host, and address properties in your
nifi.properties file.
 nifi.remote.input.socket.host=   <-- if you want to use
Remote Process groups (Site-to-Site)
 nifi.web.http.host=  or nifi.web.https.host=
 and the two above for clustering

Thanks,
Matt

On Mon, Feb 15, 2016 at 1:09 PM, Sai Kasturi 
wrote:

> Hi,
>
> I am very new to Nifi, and have been trying to get my head around the
> concept of clustering. I tried to create a cluster using VM's. I had the
> manager on one VM, the node on the other VM. Now, the cluster was not
> working(not even connecting). Then I added a node instance in the first VM,
> after which the cluster is successfully established. Also, when I shutdown
> the node instance on the first VM the whole cluster is gone.
>
> My doubt is "Do we need to have a node instance on the machine where the
> Cluster manager is" definitely??
>
>
>
>
>
> -
> Sai K
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/NCM-and-node-on-the-same-machine-tp7353.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>

NCM and node on the same machine?

[Sai Kasturi]

Hi,

I am very new to Nifi, and have been trying to get my head around the
concept of clustering. I tried to create a cluster using VM's. I had the
manager on one VM, the node on the other VM. Now, the cluster was not
working(not even connecting). Then I added a node instance in the first VM,
after which the cluster is successfully established. Also, when I shutdown
the node instance on the first VM the whole cluster is gone.

My doubt is "Do we need to have a node instance on the machine where the
Cluster manager is" definitely??





-
Sai K
--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/NCM-and-node-on-the-same-machine-tp7353.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

[GitHub] nifi pull request: NIFI-1464, NIFI-78, NIFI-1487 Refactored Proces...

[apiri]

Github user apiri commented on a diff in the pull request:

https://github.com/apache/nifi/pull/210#discussion_r52926955
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/StandardProcessScheduler.java
 ---
@@ -288,171 +284,74 @@ public void run() {
 }
 
 /**
- * Starts scheduling the given processor to run after invoking all 
methods on the underlying {@link org.apache.nifi.processor.Processor
- * FlowFileProcessor} that are annotated with the {@link OnScheduled} 
annotation.
+ * Starts the given {@link Processor} by invoking its
+ * {@link ProcessorNode#start(ScheduledExecutorService, long, 
org.apache.nifi.processor.ProcessContext, Runnable)}
+ * .
+ * @see StandardProcessorNode#start(ScheduledExecutorService, long,
+ *  org.apache.nifi.processor.ProcessContext, Runnable).
  */
 @Override
 public synchronized void startProcessor(final ProcessorNode procNode) {
-if (procNode.getScheduledState() == ScheduledState.DISABLED) {
--- End diff --

No worries and no rush.  Thanks!


---
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.
---

[GitHub] nifi pull request: NIFI-1464, NIFI-78, NIFI-1487 Refactored Proces...

[olegz]

Github user olegz commented on a diff in the pull request:

https://github.com/apache/nifi/pull/210#discussion_r52926642
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/StandardProcessScheduler.java
 ---
@@ -288,171 +284,74 @@ public void run() {
 }
 
 /**
- * Starts scheduling the given processor to run after invoking all 
methods on the underlying {@link org.apache.nifi.processor.Processor
- * FlowFileProcessor} that are annotated with the {@link OnScheduled} 
annotation.
+ * Starts the given {@link Processor} by invoking its
+ * {@link ProcessorNode#start(ScheduledExecutorService, long, 
org.apache.nifi.processor.ProcessContext, Runnable)}
+ * .
+ * @see StandardProcessorNode#start(ScheduledExecutorService, long,
+ *  org.apache.nifi.processor.ProcessContext, Runnable).
  */
 @Override
 public synchronized void startProcessor(final ProcessorNode procNode) {
-if (procNode.getScheduledState() == ScheduledState.DISABLED) {
--- End diff --

Sure, sorry in route to NYC, but will look once back online, but definitely 
up for it


---
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.
---

[GitHub] nifi pull request: NIFI-1464, NIFI-78, NIFI-1487 Refactored Proces...

[apiri]

Github user apiri commented on a diff in the pull request:

https://github.com/apache/nifi/pull/210#discussion_r52926373
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/StandardProcessScheduler.java
 ---
@@ -288,171 +284,74 @@ public void run() {
 }
 
 /**
- * Starts scheduling the given processor to run after invoking all 
methods on the underlying {@link org.apache.nifi.processor.Processor
- * FlowFileProcessor} that are annotated with the {@link OnScheduled} 
annotation.
+ * Starts the given {@link Processor} by invoking its
+ * {@link ProcessorNode#start(ScheduledExecutorService, long, 
org.apache.nifi.processor.ProcessContext, Runnable)}
+ * .
+ * @see StandardProcessorNode#start(ScheduledExecutorService, long,
+ *  org.apache.nifi.processor.ProcessContext, Runnable).
  */
 @Override
 public synchronized void startProcessor(final ProcessorNode procNode) {
-if (procNode.getScheduledState() == ScheduledState.DISABLED) {
--- End diff --

Yeah, we are good here.  I mentioned on the backing ticket, but would you 
also be up for updating the developer's guide with the changes you have 
employed?


---
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: [DISCUSS] git branching model

[Benson Margulies]

The issue tracker
https://ecosystem.atlassian.net/projects/MJF/issues/MJF-259?filter=allopenissues
might also prove useful in evaluating it.

On Mon, Feb 15, 2016 at 12:03 PM, Benson Margulies
 wrote:
> I tried to use the bitbucket gitflow plugin. It worked great, until it
> didn't. It would get into terrible, inexplicable, merge problems. No
> one seemed to be maintaining it.
>
> There's a new offering in this dept:
> https://github.com/egineering-llc/gitflow-helper-maven-plugin.
>
> On Mon, Feb 15, 2016 at 11:41 AM, Adam Taft  wrote:
>> One of the harder things with gitflow is using it in combination with
>> maven.  It's ideal that the tags and releases are tracking closely with the
>> maven pom.xml version.  gitflow, on its own, doesn't keep the pom version
>> updated with the git release names.
>>
>> Because of the general importance of keeping releases and tags synchronized
>> with the pom version, I think whatever we do, it needs to be approached
>> with tools that are available through maven rather than from git.  The
>> git-flow plugin (referenced by Thad) doesn't directly help deal with this
>> synchronization, since it's a git tool, not a maven tool.
>>
>> I've been using, with reasonable success, the jgitflow [1] plugin, which
>> does a reasonable job of following the gitflow model for a maven project.
>> I don't recommend this plugin for NIFI, because it insists that the master
>> branch is strictly used for published release tags (as per the strict
>> gitflow workflow).  I just mention this, in reference to how some plugins
>> are tackling the gitflow and maven synchronization issue.
>>
>> [1] http://jgitflow.bitbucket.org/
>>
>>
>> On Sun, Feb 14, 2016 at 10:48 PM, Thad Guidry  wrote:
>>
>>> Your on the right track / idea with Git-flow.  Your Master become primary
>>> development of next release (with feature branches off of it).. while you
>>> continue to have release branches that can have hot fix branches off of
>>> them.  (don't use Master as your release branch ! - bad practice ! )
>>>
>>> Here is the Git-flow cheat sheet to make it easy for everyone to
>>> understand... just scroll it down to gain the understanding. Its really
>>> that easy.
>>>
>>> http://danielkummer.github.io/git-flow-cheatsheet/
>>>
>>> Most large projects have moved into using git-flow ... and tools like
>>> Eclipse Mars, IntelliJ, Sourcetree, etc...have Git-flow either built in or
>>> plugin available now.  If you want to live on the command line, then that
>>> is handled easily by the instructions in the above link.
>>>
>>> Thad
>>> +ThadGuidry 
>>>

Re: [DISCUSS] git branching model

[Adam Taft]

One of the harder things with gitflow is using it in combination with
maven.  It's ideal that the tags and releases are tracking closely with the
maven pom.xml version.  gitflow, on its own, doesn't keep the pom version
updated with the git release names.

Because of the general importance of keeping releases and tags synchronized
with the pom version, I think whatever we do, it needs to be approached
with tools that are available through maven rather than from git.  The
git-flow plugin (referenced by Thad) doesn't directly help deal with this
synchronization, since it's a git tool, not a maven tool.

I've been using, with reasonable success, the jgitflow [1] plugin, which
does a reasonable job of following the gitflow model for a maven project.
I don't recommend this plugin for NIFI, because it insists that the master
branch is strictly used for published release tags (as per the strict
gitflow workflow).  I just mention this, in reference to how some plugins
are tackling the gitflow and maven synchronization issue.

[1] http://jgitflow.bitbucket.org/


On Sun, Feb 14, 2016 at 10:48 PM, Thad Guidry  wrote:

> Your on the right track / idea with Git-flow.  Your Master become primary
> development of next release (with feature branches off of it).. while you
> continue to have release branches that can have hot fix branches off of
> them.  (don't use Master as your release branch ! - bad practice ! )
>
> Here is the Git-flow cheat sheet to make it easy for everyone to
> understand... just scroll it down to gain the understanding. Its really
> that easy.
>
> http://danielkummer.github.io/git-flow-cheatsheet/
>
> Most large projects have moved into using git-flow ... and tools like
> Eclipse Mars, IntelliJ, Sourcetree, etc...have Git-flow either built in or
> plugin available now.  If you want to live on the command line, then that
> is handled easily by the instructions in the above link.
>
> Thad
> +ThadGuidry 
>

RE: EXTERNAL: Re: OutofMemory

[Gresock, Joseph]

Thanks Corey.  I'll try that, but I'm wondering what the 
nifi.components.status.snapshot.frequency does.  Would decreasing that time (1 
min) make it take snapshots more frequently, and would this have the effect of 
decreasing or increasing the memory used?  I did decrease the 
nifi.components.status.repository.buffer.size to 180 and I'll see how that 
behaves.



Joe

-Original Message-
From: Corey Flowers [mailto:cflow...@onyxpoint.com] 
Sent: Monday, February 15, 2016 10:32 AM
To: dev@nifi.apache.org
Subject: EXTERNAL: Re: OutofMemory

Hey Joseph,

  I have a couple of clusters in the 600-1200 range and they have
16-32 GB jvm heap sizes respectfully. Really it depends on what processors you 
are using and your volumes. One thing that may help a little is to decrease 
your number of stored statics in the graph.
There are two properties in the conf file, one is set to 1440 and the other is 
a time, which is every 1 min. I believe these stats are stored in the heap 
space. Devs correct me if I am wrong. You could lessen the time and amount to 
buy you a little space. I don't think this is a solution, really it is more of 
a band-aide.

Good luck!





Sent from my iPhone

> On Feb 15, 2016, at 9:33 AM, Gresock, Joseph  wrote:
>
> Devs,
>
> We've been seeing some OutOfMemoryErrors on the NCM of our 10-node cluster 
> recently.  The flow has ~600 processors, and the NCM runs on a VM with 8GB 
> RAM.  We have 6G allocated to the Nifi JVM on this node.
>
> The specific log message we see is:
>
> WARN [Process NCM Request-6] org.apache.nifi.io.socket.SocketListener 
> Dispatching socket request encountered exception due to: 
> java.lang.OutOfMemoryError: Java heap space
>
> First, I'm hoping there's some advice on how to avoid this in the first 
> place, but barring that, is there a way to configure Nifi to auto-restart the 
> NCM when it gets this error?  I seem to remember seeing this in the past, but 
> I couldn't find anything in bootstrap.conf or nifi.properties that looked 
> related.
>
> Thanks,
> Joe

Re: OutofMemory

[Corey Flowers]

Hey Joseph,

  I have a couple of clusters in the 600-1200 range and they have
16-32 GB jvm heap sizes respectfully. Really it depends on what
processors you are using and your volumes. One thing that may help a
little is to decrease your number of stored statics in the graph.
There are two properties in the conf file, one is set to 1440 and the
other is a time, which is every 1 min. I believe these stats are
stored in the heap space. Devs correct me if I am wrong. You could
lessen the time and amount to buy you a little space. I don't think
this is a solution, really it is more of a band-aide.

Good luck!





Sent from my iPhone

> On Feb 15, 2016, at 9:33 AM, Gresock, Joseph  wrote:
>
> Devs,
>
> We've been seeing some OutOfMemoryErrors on the NCM of our 10-node cluster 
> recently.  The flow has ~600 processors, and the NCM runs on a VM with 8GB 
> RAM.  We have 6G allocated to the Nifi JVM on this node.
>
> The specific log message we see is:
>
> WARN [Process NCM Request-6] org.apache.nifi.io.socket.SocketListener 
> Dispatching socket request encountered exception due to: 
> java.lang.OutOfMemoryError: Java heap space
>
> First, I'm hoping there's some advice on how to avoid this in the first 
> place, but barring that, is there a way to configure Nifi to auto-restart the 
> NCM when it gets this error?  I seem to remember seeing this in the past, but 
> I couldn't find anything in bootstrap.conf or nifi.properties that looked 
> related.
>
> Thanks,
> Joe

Re: Issues while using python script in Apache NIFI for ExecuteStreamCommand processor

[Mark Payne]

Anurag,

Your Python script should not need to know about FlowFiles. Rather, the content 
of the FlowFile
will be streamed to the Python script's "Standard In" and whatever the script 
writes to "Standard Out"
will become the new content of the FlowFile.

Does this make sense?

Thanks
-Mark


> On Feb 15, 2016, at 9:24 AM, anurag sharma  wrote:
> 
> Hi,
> 
> I am trying to use python script in Apache NIFI for ExecuteStreamCommand
> processor, but its not working properly.
> I don't know how to read data from FlowFile and how to create FlowFile in
> Python script.
> Could you please provide me a sample python script.
> 
> I found your email from the below page:
> https://mail-archives.apache.org/mod_mbox/nifi-dev/201506.mbox/%3ccadt6bvsnukrjhldrtz29wmqkd85xjmqgykgqcpw881wvost...@mail.gmail.com%3E
> 
> Thanks & Reagrds,
> Anurag

Re: [VOTE] Release Apache NiFi 0.5.0 (RC3)

[Lars Francke]

+1 (non-binding)

Builds okay and ran some basic flows including some basic testing of the
state management

On Sat, Feb 13, 2016 at 12:27 AM, Tony Kurc  wrote:

> Hello
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-0.5.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1073
>
>
> The Git tag is nifi-0.5.0-RC3
> The Git commit ID is 8309dba80bbc0e6c0dfe5b8f93750d424f5b9a90
>
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=8309dba80bbc0e6c0dfe5b8f93750d424f5b9a90
>
> This release candidate is a branch off of master at
> cae5b109c09be80df77f2d767220b82850178ed5.
>
> Checksums of nifi-0.5.0-source-release.zip:
> MD5: 5d20a5bb2fcdb3d96b2c62949db1c780
> SHA1: e1c541d27373b94a58c8ede4eae7f6a7eb51c5a0
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/tkurc.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> 106 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12334158
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.5.0
>
> Migration guidance can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
>
> The vote will be open for 96 hours (24 extra hours due to late Friday
> release candidate)
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  The
> please vote:
>
> [ ] +1 Release this package as nifi-0.5.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

[GitHub] nifi pull request: NIFI-1464, NIFI-78, NIFI-1487 Refactored Proces...

[olegz]

Github user olegz commented on a diff in the pull request:

https://github.com/apache/nifi/pull/210#discussion_r52907459
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/test/java/org/apache/nifi/controller/service/TestStandardControllerServiceProvider.java
 ---
@@ -218,7 +221,7 @@ public void testStartStopReferencingComponents() {
 public Object answer(InvocationOnMock invocation) throws 
Throwable {
 final ProcessorNode procNode = (ProcessorNode) 
invocation.getArguments()[0];
 procNode.verifyCanStart();
-procNode.setScheduledState(ScheduledState.RUNNING);
+// procNode.setScheduledState(ScheduledState.RUNNING);
--- End diff --

True, and I think this test(s) may need to be removed since tests that I 
added as part of the refactoring efforts cover all possible scenarios without 
Mocks. And if for some reason you'll find a missing scenario, let me know and 
I'll add a test.


---
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.
---

[GitHub] nifi pull request: NIFI-1464, NIFI-78, NIFI-1487 Refactored Proces...

[olegz]

Github user olegz commented on a diff in the pull request:

https://github.com/apache/nifi/pull/210#discussion_r52907228
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/StandardProcessScheduler.java
 ---
@@ -288,171 +284,74 @@ public void run() {
 }
 
 /**
- * Starts scheduling the given processor to run after invoking all 
methods on the underlying {@link org.apache.nifi.processor.Processor
- * FlowFileProcessor} that are annotated with the {@link OnScheduled} 
annotation.
+ * Starts the given {@link Processor} by invoking its
+ * {@link ProcessorNode#start(ScheduledExecutorService, long, 
org.apache.nifi.processor.ProcessContext, Runnable)}
+ * .
+ * @see StandardProcessorNode#start(ScheduledExecutorService, long,
+ *  org.apache.nifi.processor.ProcessContext, Runnable).
  */
 @Override
 public synchronized void startProcessor(final ProcessorNode procNode) {
-if (procNode.getScheduledState() == ScheduledState.DISABLED) {
--- End diff --

So I am assuming we're cool or should I still explain?


---
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.
---

OutofMemory

[Gresock, Joseph]

Devs,

We've been seeing some OutOfMemoryErrors on the NCM of our 10-node cluster 
recently.  The flow has ~600 processors, and the NCM runs on a VM with 8GB RAM. 
 We have 6G allocated to the Nifi JVM on this node.

The specific log message we see is:

WARN [Process NCM Request-6] org.apache.nifi.io.socket.SocketListener 
Dispatching socket request encountered exception due to: 
java.lang.OutOfMemoryError: Java heap space

First, I'm hoping there's some advice on how to avoid this in the first place, 
but barring that, is there a way to configure Nifi to auto-restart the NCM when 
it gets this error?  I seem to remember seeing this in the past, but I couldn't 
find anything in bootstrap.conf or nifi.properties that looked related.

Thanks,
Joe