jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "fabrizio giustina (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-160) Query index not in sync with workspace
Date Tue, 12 Jul 2005 15:58:13 GMT
    [ http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12315599 ] 

fabrizio giustina commented on JCR-160:
---------------------------------------

Updated jackrabbit to rev. 215946.
With the same currupted index I don't get any error anymore, only a warning log for the missing
nodes:

WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:45:11
-- Node e6c5b588-50a5-4148-afbd-f7ff95104d36 does not exist anymore: javax.jcr.ItemNotFoundException:
e6c5b588-50a5-4148-afbd-f7ff95104d36
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:45:12
-- Node b14139fb-01ab-492d-a465-e183cb43b484 does not exist anymore: javax.jcr.ItemNotFoundException:
b14139fb-01ab-492d-a465-e183cb43b484
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:45:12
-- Node 7bb7855c-8317-40fd-b3b8-2cc27bb555db does not exist anymore: javax.jcr.ItemNotFoundException:
7bb7855c-8317-40fd-b3b8-2cc27bb555db
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:45:54
-- Node b14139fb-01ab-492d-a465-e183cb43b484 does not exist anymore: javax.jcr.ItemNotFoundException:
b14139fb-01ab-492d-a465-e183cb43b484
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:46:06
-- Node e6c5b588-50a5-4148-afbd-f7ff95104d36 does not exist anymore: javax.jcr.ItemNotFoundException:
e6c5b588-50a5-4148-afbd-f7ff95104d36
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:46:06
-- Node b14139fb-01ab-492d-a465-e183cb43b484 does not exist anymore: javax.jcr.ItemNotFoundException:
b14139fb-01ab-492d-a465-e183cb43b484
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:46:06
-- Node 7bb7855c-8317-40fd-b3b8-2cc27bb555db does not exist anymore: javax.jcr.ItemNotFoundException:
7bb7855c-8317-40fd-b3b8-2cc27bb555db
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:46:58
-- Node f3b725ae-bab7-438b-9576-abb1cf65ffeb does not exist anymore: javax.jcr.ItemNotFoundException:
f3b725ae-bab7-438b-9576-abb1cf65ffeb
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:46:58
-- Node 5852da20-2adb-4a20-8856-bd2d29023e9d does not exist anymore: javax.jcr.ItemNotFoundException:
5852da20-2adb-4a20-8856-bd2d29023e9d
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node c0853856-766d-46ed-b40d-4a781a2c798a does not exist anymore: javax.jcr.ItemNotFoundException:
c0853856-766d-46ed-b40d-4a781a2c798a
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 7bb7855c-8317-40fd-b3b8-2cc27bb555db does not exist anymore: javax.jcr.ItemNotFoundException:
7bb7855c-8317-40fd-b3b8-2cc27bb555db
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 96e901e6-68e3-4807-8eb5-14cadb732ec9 does not exist anymore: javax.jcr.ItemNotFoundException:
96e901e6-68e3-4807-8eb5-14cadb732ec9
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 26f9fdd6-1aba-43c9-99d7-8ceef89cfcbf does not exist anymore: javax.jcr.ItemNotFoundException:
26f9fdd6-1aba-43c9-99d7-8ceef89cfcbf
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 0bbbd9de-cd5e-48b1-95b3-8e1f51ddb199 does not exist anymore: javax.jcr.ItemNotFoundException:
0bbbd9de-cd5e-48b1-95b3-8e1f51ddb199
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 436c5b31-bfcb-4e91-8d92-b8763ced742c does not exist anymore: javax.jcr.ItemNotFoundException:
436c5b31-bfcb-4e91-8d92-b8763ced742c
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 8572edac-0783-4a1d-a1b7-41431ffcf999 does not exist anymore: javax.jcr.ItemNotFoundException:
8572edac-0783-4a1d-a1b7-41431ffcf999
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node cca4774f-18a7-4f3b-ba9f-2207af630a45 does not exist anymore: javax.jcr.ItemNotFoundException:
cca4774f-18a7-4f3b-ba9f-2207af630a45
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node 90f036dc-83fc-448e-a467-3c608b23976f does not exist anymore: javax.jcr.ItemNotFoundException:
90f036dc-83fc-448e-a467-3c608b23976f
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node b14139fb-01ab-492d-a465-e183cb43b484 does not exist anymore: javax.jcr.ItemNotFoundException:
b14139fb-01ab-492d-a465-e183cb43b484
WARN   org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl 12.07.2005 17:47:02
-- Node c244633b-ff6c-43ef-843d-cd343b29ff61 does not exist anymore: javax.jcr.ItemNotFoundException:
c244633b-ff6c-43ef-843d-cd343b29ff61


A lot better now, the latest enhancement could be removing any invalid node found during the
search... since the index can be easily corrupted by a forced shutdown or an OutOfMemoryError
I think there is no way to be totally sure that this will never happen: a "self-reparing"
index could probably be the better solution.

Thanks, good work!




> Query index not in sync with workspace
> --------------------------------------
>
>          Key: JCR-160
>          URL: http://issues.apache.org/jira/browse/JCR-160
>      Project: Jackrabbit
>         Type: Bug
>   Components: query
>     Reporter: Marcel Reutegger
>     Assignee: Marcel Reutegger
>      Fix For: 1.0

>
> After some time the search index is not in sync anymore with the data in the workspace
and returns uuids which have no corresponding Node in the workspace. This results in a NodeIterator
which throws an ItemNotFoundException on nextNode().
> Instructions how to reproduce this error are not yet available.
> Possible areas for further investigation are:
> - NodeType registry which maps the node types into the workspace with the use of virtual
item states
> - versioning?
> - atomicity of indexing?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message