Hi Julian,
The LastRevRecoveryAgent is executed at 2 places
1. On DocumentNodeStore startup where the MissingLastRevSeeker is used to
get potential candidates for recovery.
2. At regular intervals defined by the property
'lastRevRecoveryJobIntervalInSecs' in the DocumentNodeStoreService (default
On 2014-08-26 08:03, Amit Jain wrote:
Hi Julian,
The LastRevRecoveryAgent is executed at 2 places
1. On DocumentNodeStore startup where the MissingLastRevSeeker is used to
get potential candidates for recovery.
2. At regular intervals defined by the property
'lastRevRecoveryJobIntervalInSecs
the MissingLastRevSeeker is used to
get potential candidates for recovery.
2. At regular intervals defined by the property
'lastRevRecoveryJobIntervalInSecs' in the DocumentNodeStoreService
(default
60 seconds). Short description is that MissingLastRevSeeker will be called
rarely in this case.
Long
startup where the MissingLastRevSeeker is used
to
get potential candidates for recovery.
2. At regular intervals defined by the property
'lastRevRecoveryJobIntervalInSecs' in the DocumentNodeStoreService
(default
60 seconds). Short description is that MissingLastRevSeeker will be
called
,
The LastRevRecoveryAgent is executed at 2 places
1. On DocumentNodeStore startup where the MissingLastRevSeeker is used
to
get potential candidates for recovery.
2. At regular intervals defined by the property
'lastRevRecoveryJobIntervalInSecs' in the DocumentNodeStoreService
(default
60
On 2014-08-26 08:03, Amit Jain wrote:
Hi Julian,
The LastRevRecoveryAgent is executed at 2 places
1. On DocumentNodeStore startup where the MissingLastRevSeeker is used to
get potential candidates for recovery.
Sure? I've been logging it, and I don't see it called on every startup
On 2014-08-26 11:32, Amit Jain wrote:
Hi,
I was proposing the additional method for cases where we want to query the
indexed properties other than _id like needed in MongoBlobReferenceIterator
and MongoMissingLastRevSeeker.
But,
Can't we use this method to at least narrow down the query to
Hi there,
it appears that the MissingLastRevSeeker (oak-core), when run, will be
very slow on large repos, unless they use a MongoDocumentStore (which
has a special-cased query).
Question: when will this code execute? I've seen it occasionally during
benchmarking, but it doesn't seem
