[
https://issues.apache.org/jira/browse/NIFI-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062271#comment-15062271
]
Oleg Zhurakousky commented on NIFI-1287:
----------------------------------------
Downgrading it to minor and will change the title since it really isn't a
deadlock, rather inefficient thread utilization. Will provide more details in
the PR whenever its ready
> VolatileContentRepository deadlocks in certain scenarios
> --------------------------------------------------------
>
> Key: NIFI-1287
> URL: https://issues.apache.org/jira/browse/NIFI-1287
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.0
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Priority: Minor
> Fix For: 0.5.0
>
>
> Still investigating details but here is what I see:
> {code}VolatileContentRepository Workers Thread-3" #127 daemon prio=5
> os_prio=31 tid=0x00007ff608112800 nid=0x6403 waiting on condition
> [0x000000011fdac000]
> java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x0000000780262190> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
> at
> java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
> at
> org.apache.nifi.controller.repository.claim.StandardResourceClaimManager.drainDestructableClaims(StandardResourceClaimManager.java:131)
> at
> org.apache.nifi.controller.repository.VolatileContentRepository$CleanupOldClaims.run(VolatileContentRepository.java:654)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
