-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
3.4.7, 4.2.5, 4.3
-
Studio 2.4
-
13
-
Severity 3 - Minor
-
2
-
This problem only happened in a recently installed instance after restoring a database dump that had (possibly) a different timezone from the running server, so that the table contents got created with a future timestamp, that led to a unexpected behavior on the com.atlassian.confluence.search.lucene.queue.DatabaseIndexTaskQueue where the '<CONF_HOME>/index/.timestamp' file was created with a date in the future. The consequence was that every time the indexing job ran it couldn't retrieve the new items on the queue to be indexed, resulting in a instance where no content was automatically indexed.
A workaround was re-indexing manually, a definitive solution was correcting the timestamps on the table, removing the '.timestamp' file and restaring the instance.
Some debug info available at: https://studio.atlassian.com/browse/JST-3712
Workaround
http://confluence.atlassian.com/display/CONFKB/Confluence+Fails+to+Process+Index+Queue+Automatically
- mentioned in
-
Page Failed to load
[CONFSERVER-21720] Automatic indexing doesn't work if the creationdate column on the INDEXQUEUEENTRIES table has values in the future
QA Demo Status | New: Not Needed [ 14332 ] | |
QA Kickoff Status | New: Not Needed [ 14236 ] | |
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | Original: affects-server ondemand searching/indexing | New: affects-server cleanup-seos-fy25 ondemand searching/indexing |
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 139465 ] |
UIS | Original: 1 | New: 2 |
UIS | Original: 2 | New: 1 |
UIS | Original: 1 | New: 2 |
UIS | Original: 2 | New: 1 |
Support reference count | Original: 8 | New: 13 |
Support reference count | Original: 13 | New: 8 |
Remote Link | New: This issue links to "Page (Confluence)" [ 479204 ] |