Details
-
Bug
-
Resolution: Fixed
-
High
-
No-Version
-
2
-
Severity 1 - Critical
-
4
-
Description
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
CQ appears to be waiting for a lock that is locked by the index, which is currently trying to process a large amount of updates.
"http-nio-8081-exec-3" #252 daemon prio=5 os_prio=0 tid=0x00007f8bbc15e800 nid=0x1f91 waiting on condition [0x00007f8930951000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00000005e0802508> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) ... at com.atlassian.bonnie.LoggingReentrantLock.lock(LoggingReentrantLock.java:32) at com.atlassian.bonnie.LuceneConnection.withWriter(LuceneConnection.java:483)
The thread 'http-nio-8081-exec-3 is a doeditquestion.action:
| Thread ID | Thread name | User ID | Type | Summary | Duration |
|---|---|---|---|---|---|
| 252 | http-nio-8081-exec-3 | amckague | web-request | /cq/doeditquestion.action?id=2669904138 | 1 hour, 16 minutes, 20 seconds |
The only threads that are getting stuck are CQ threads (see screenshot). Why would we be blocking on a Lucene lock in CQ?
Impact of this bug
This bug can cause threads to become stuck, which means indexing does not occur, and questions/answers cannot be posted to Confluence Questions (they simply hang). A restart of the instance (or a rolling restart of the full cluster) is required to resolve it.
It can also cause indexing to be delayed after a restart, by up to 20m, depending on the size of your instance.
Attachments
Issue Links
- has a regression in
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
-
HOT-36493 Loading...
-
- is related to
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Wiki Page
-