Re: Jackrabbit OAK property index never used ?

[Thomas Mueller]

Hi,

I think you are hitting OAK-2852.

Regards,
Thomas



On 23/09/15 11:42, "Thomas Mueller"  wrote:

>Hi,
>
>Do you have a node called /oak:index/counter ? Out of the-box, it should
>be there (with a recent version of Oak). That is the approximate counter
>index that is used to estimate how many nodes to traverse. As a
>workaround, you probably have to re-index that one manually. I wonder why
>that index is not updated in your case, it is a regular asynchronous
>index.
>
>Regards,
>Thomas
>
>
>On 22/09/15 17:04, "Sebastien Berthezene"  wrote:
>
>>Because 2000 (not corresponding to reality) is lower than 12702 from my
>>property index, the traversal mode is used.
>

Re: Jackrabbit OAK property index never used ?

[Sebastien Berthezene]

Thanks for your help but I have the node "/oak:index/counter". Dump of node
get with "session.getNodeByIdentifier("/oak:index/counter")" is the
following :
type = counter
async = async
jcr:primaryType = oak:QueryIndexDefinition

>From what i understand it seems that node count is not set (is it supposed
to be set somewhere ?) and so traversal index use a default hardcoded value
corresponding to ApproximateCounter.COUNT_RESOLUTION * 20 ( = 2000) always
lower than node count managed by my property index. How could i fix this
node count supposed to be stored into a ":count" property ?

Regards

2015-09-23 12:15 GMT+02:00 Thomas Mueller :

> Hi,
>
> I think you are hitting OAK-2852.
>
> Regards,
> Thomas
>
>
>
> On 23/09/15 11:42, "Thomas Mueller"  wrote:
>
> >Hi,
> >
> >Do you have a node called /oak:index/counter ? Out of the-box, it should
> >be there (with a recent version of Oak). That is the approximate counter
> >index that is used to estimate how many nodes to traverse. As a
> >workaround, you probably have to re-index that one manually. I wonder why
> >that index is not updated in your case, it is a regular asynchronous
> >index.
> >
> >Regards,
> >Thomas
> >
> >
> >On 22/09/15 17:04, "Sebastien Berthezene"  wrote:
> >
> >>Because 2000 (not corresponding to reality) is lower than 12702 from my
> >>property index, the traversal mode is used.
> >
>
>

jackrabbit-oak build #6491: Broken

[Travis CI]

Build Update for apache/jackrabbit-oak
-

Build: #6491
Status: Broken

Duration: 484 seconds
Commit: 89fc9a295e0b597a80d78211b782dab98c848e89 (trunk)
Author: Thomas Mueller
Message: OAK-301: Document Oak

git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/trunk@1704861 
13f79535-47bb-0310-9956-ffa450edef68

View the changeset: 
https://github.com/apache/jackrabbit-oak/compare/a3cfa2c96bb7...89fc9a295e0b

View the full build log and details: 
https://travis-ci.org/apache/jackrabbit-oak/builds/81787673

--
sent by Jukka's Travis notification gateway

Builds timing out on Jenkins

[Michael Dürig]

Hi,

I started seeing builds timing out (after 90mins) on Jenkins [1]. So far 
I think this affected the DOCUMENT_RDB fixture only. Julian, how long 
should such builds take? As I also have seen OOME in this area, might we 
run under memory pressure?


Michael


[1] 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/431/jdk=latest1.7,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=integrationTesting/console

[2]

jackrabbit-oak build #6492: Fixed

[Travis CI]

Build Update for apache/jackrabbit-oak
-

Build: #6492
Status: Fixed

Duration: 1653 seconds
Commit: f38f37113504ef51267c0371c33ff5225412324e (trunk)
Author: Francesco Mari
Message: OAK-3441 - SecurityProviderImpl should not be an OSGi component


git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/trunk@1704886 
13f79535-47bb-0310-9956-ffa450edef68

View the changeset: 
https://github.com/apache/jackrabbit-oak/compare/89fc9a295e0b...f38f37113504

View the full build log and details: 
https://travis-ci.org/apache/jackrabbit-oak/builds/81800227

--
sent by Jukka's Travis notification gateway

Re: Builds timing out on Jenkins

[Julian Reschke]

On 2015-09-23 17:49, Michael Dürig wrote:


Hi,

I started seeing builds timing out (after 90mins) on Jenkins [1]. So far
I think this affected the DOCUMENT_RDB fixture only. Julian, how long
should such builds take? As I also have seen OOME in this area, might we
run under memory pressure?

Michael


I don't have any numbers ready but note that the performance of the 
various build machines seems to vary. For the same build the 
DOCUMENT_RDB build for JDK8 only took 14 minutes...


I'll try to get a rough estimate on my machine, but that will take some 
time as it interferes with normal work...


Best regards, Julian

Re: Jackrabbit OAK property index never used ?

[Thomas Mueller]

Hi,

Do you have a node called /oak:index/counter ? Out of the-box, it should
be there (with a recent version of Oak). That is the approximate counter
index that is used to estimate how many nodes to traverse. As a
workaround, you probably have to re-index that one manually. I wonder why
that index is not updated in your case, it is a regular asynchronous index.

Regards,
Thomas


On 22/09/15 17:04, "Sebastien Berthezene"  wrote:

>Because 2000 (not corresponding to reality) is lower than 12702 from my
>property index, the traversal mode is used.

Re: svn commit: r1704844 - in /jackrabbit/oak/trunk: oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/counter/jmx/ oak-core/src/main/java/org/apache/jackrabbit/oak/query/ oak-core/src/ma

[Chetan Mehrotra]

Hi Thomas,

On Wed, Sep 23, 2015 at 6:51 PM,   wrote:
>  /**
> + * Get the index cost. The query must already be prepared.
> + *
> + * @return the index cost
> + */
> +String getIndexCost();

Should this be returning string? May be we should name it better

Chetan Mehrotra