[
https://issues.apache.org/jira/browse/JCR-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606698#action_12606698
]
Jukka Zitting commented on JCR-1657:
------------------------------------
Looks good to me.
> Cluster revision entries should be retrieved in order
> -----------------------------------------------------
>
> Key: JCR-1657
> URL: https://issues.apache.org/jira/browse/JCR-1657
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.3.3
> Environment: Clustered
> Reporter: Martijn Hendriks
> Assignee: Martijn Hendriks
> Attachments: JCR-1657.patch
>
>
> The selectRevisionStmtSQL (DatabaseJournal#buildSqlStatements) returns a
> result set which may not be ordered by REVISION_ID. This has the effect that
> cluster instances that want to synchronize to the latest revision do not
> update their local revision appropriately since they assume that the revision
> result set is ordered (see code in AbstractJournal#doSync). This might cause
> a lot of unnecessary CPU cycles on these machines with degraded performance
> as a result. Furthermore, it causes functional issues as well as events may
> be fired multiple times and in the wrong order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
