[ 
https://issues.apache.org/jira/browse/NIFI-10258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571543#comment-17571543
 ] 

Joe Witt commented on NIFI-10258:
---------------------------------

[~cdeepakreddy20] You'll need to determine what the best course of action is to 
meet your systems requirements/obligations.  But NiFi cannot have an external 
process injecting itself into its file handling operations for its repositories 
or we cannot reason over what the result would be.  I would disable such virus 
scanning for the flowfile, content, and provenance repositories as well as the 
log directory and h2-database directory.  Given the information you've shared 
so far this is likely the problem and the solution to it.

If you have data going through the flow which you're concerned about from a 
virus scanning point of view it is perfectly fine and often done that a 
processor in the flow would stream the content to a virus scanning endpoint and 
identify whether any hits are present.  I have no specific guidance to share on 
that but it has been done by many and is pretty powerful.  This is a little 
different than the above paragraph about disable live scanning of these various 
locations but wanted to mention this.  

Thanks

> Continuously getting the error "ERROR: Failed to index Provenance Events. See 
> logs for more information. " in the Bulletin Board
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-10258
>                 URL: https://issues.apache.org/jira/browse/NIFI-10258
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.15.3
>         Environment: Operating System: Red Hat Enterprise Linux Server 7.9 
> (Maipo)
> Architecture: amd 64
> Kernel: Linux 3.10.0-1160.53.1.el7.x86_64
> Java Version:1.8.0_322
>            Reporter: Deepak Reddy Chirthani
>            Priority: Critical
>         Attachments: Nifi_logs_deepak.txt, Provenance_properties.PNG
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> we have started to use the reporting task *SiteToSiteProvenanceReportingTask 
> 1.15.3* for auditing purposes on provenance events for a few of our 
> dataflows. We started to see error quite frequently now in the Bulletin Board.
> *ERROR: Failed to index Provenance Events. See logs for more information.*
> Also, below are attached snaps of nifi.provenance.properties file and from 
> logs regarding this error. 
> Please let me know if you need anything more.
> Update: Even though S2SProvenanceReportingTask is stopped, the error still 
> exisits.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to