jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-905) Clustering: race condition may cause duplicate entries in search index
Date Mon, 09 Jul 2007 13:21:04 GMT

    [ https://issues.apache.org/jira/browse/JCR-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511114

Jukka Zitting commented on JCR-905:

Dominique/Marcel, do you see any potential regressions with this patch? I'm not confident
enough to apply it in 1.3.1, but it sounds like it definitely should go in trunk before 1.4.

> Clustering: race condition may cause duplicate entries in search index
> ----------------------------------------------------------------------
>                 Key: JCR-905
>                 URL: https://issues.apache.org/jira/browse/JCR-905
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: clustering
>    Affects Versions: 1.3
>            Reporter: Martijn Hendriks
>         Attachments: JCR-905.patch, log1.txt, log2.txt
> There seems to be a race condition that may cause duplicate search index entries. It
is reproducible as follows (Jackrabbit 1.3):
> 1) Start clusternode 1 that just adds a single node of node type clustering:test.
> 2) Shutdown clusternode 1.
> 3) Start clusternode 2 with an empty search index.
> 4) Execute the query  //element(*, clustering:test).
> 4) Print the result of the query (UUIDs of nodes in the result set).
> When I just run clusternode 2, then there is one node in the resultset, as expected.
However, when I debug clusternode 2 and have a breakpoint (i.e., a pause of a few seconds
at line 306 of RepositoryImpl.java - just before the clusternode is started), then the resultset
contains two results, both with the same UUID.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message