Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/502
@mans2singh
Just had a new look and ran a workflow to test the processor. Few remarks
even though I am not familiar with Ignite... First, I am not sure to see how I
can check the content of what is sent to Ignite, do you have recommendation
about that?
Then, it seems that if I don't provide a configuration file, the processor
is running an embedded Ignite cache but in that case I am not sure of what is
the interest for the user. Even with a local Ignite node running it does not
seem to connect to it, normal?
Other remark, in the logs, I see some periodic status about the Ignite
instance
````
2016-06-14 22:16:25,694 INFO [grid-timeout-worker-#23%null%]
org.apache.ignite.internal.IgniteKernal
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=6b53a263, name=null, uptime=00:01:00:002]
^-- H/N/C [hosts=2, nodes=2, CPUs=16]
^-- CPU [cur=0.67%, avg=0.79%, GC=0%]
^-- Heap [used=260MB, free=49.12%, comm=512MB]
^-- Non heap [used=119MB, free=-1%, comm=125MB]
^-- Public thread pool [active=0, idle=7, qSize=0]
^-- System thread pool [active=0, idle=16, qSize=0]
^-- Outbound messages queue [size=0]
````
I don't know if it makes sens to have this kind of logs in NiFi logs,
thoughts?
Regarding the transit URI of the provenance event, I am not convinced. Is
there a way to get IP/port of the node the processor is connected to and use
this information in the event? (like, I believe, it is done in Kafka processors)
I believe there is also some kind of issues when stopping the processor: it
doesn't seem to stop gracefully and I get some stack traces when trying to run
it again... in the end, none of the incoming flow files are ingested. Here is
the stack trace if it helps
(https://gist.github.com/pvillard31/d2e97008b36b4cd9edcfec8d5ed20b86#file-putignite-log)
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
