[
https://issues.apache.org/jira/browse/NIFI-10258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569641#comment-17569641
]
Deepak Reddy Chirthani commented on NIFI-10258:
-----------------------------------------------
We have always noticed this pattern of events, when the problem starts
occurring:
1. Index Provenance Events-2 thread rolls over index due to size and starts a
new index.
2022-07-15 02:17:47,194 INFO [Index Provenance Events-2]
o.a.n.p.i.lucene.IndexDirectoryManager Size of Provenance Index at
/apps/nifi/repos/provenance_repository/lucene-8-index-1657816535950 is now
524314150. Will close this index and roll over to a new one.
2022-07-15 02:17:47,194 INFO [Index Provenance Events-2]
o.a.n.p.lucene.StandardIndexManager Index Writer for
/apps/nifi/repos/provenance_repository/lucene-8-index-1657816535950 has been
returned to Index Manager and is no longer in use. Closing Index Writer
2. Immediately after this, Index Provenance Events-1 thread tries to use the
new index, but complains about the file changed by external force.
2022-07-15 02:17:47,204 ERROR [Index Provenance Events-1]
o.a.n.p.index.lucene.EventIndexTask Failed to index Provenance Events
org.apache.lucene.store.AlreadyClosedException: Underlying file changed by an
external force at 2022-07-15T07:17:47.202562Z,
(lock=NativeFSLock(path=/apps/nifi/repos/provenance_repository/lucene-8-index-1657869467201/write.lock,impl=sun.nio.ch.FileLockImpl[0:9223372036854775807
exclusive valid],creationTime=2022-07-15T07:17:47.201562Z))
Could it be some sort of race condition where Events-1 thread starts indexing
the new file , before the Events-2 thread is done with rollover?
Should we set 'nifi.provenance.repository.index.threads' to '1' and see if the
problem persists?
> 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)
