[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-03-29 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: OAK-8177_1.patch

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-03-29 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: (was: OAK-8177_2.patch)

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-03-29 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: OAK-8177_2.patch

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-03-29 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: OAK-8177_2.patch

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch, OAK-8177_2.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-04-02 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: OAK-8177_3.patch

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch, OAK-8177_2.patch, OAK-8177_3.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-04-02 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: (was: OAK-8177_3.patch)

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch, OAK-8177_2.patch, OAK-8177_3.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-04-02 Thread Nitin Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Gupta updated OAK-8177:
-
Attachment: OAK-8177_3.patch

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Priority: Major
> Attachments: OAK-8177_1.patch, OAK-8177_2.patch, OAK-8177_3.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OAK-8177) Add logging around getReferenceCheckpoint method

2019-06-12 Thread Thomas Mueller (JIRA)


 [ 
https://issues.apache.org/jira/browse/OAK-8177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Mueller updated OAK-8177:

Labels: indexingPatch  (was: )

> Add logging around getReferenceCheckpoint method 
> -
>
> Key: OAK-8177
> URL: https://issues.apache.org/jira/browse/OAK-8177
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, lucene
>Reporter: Nitin Gupta
>Assignee: Thomas Mueller
>Priority: Major
>  Labels: indexingPatch
> Fix For: 1.12.0
>
> Attachments: OAK-8177_1.patch, OAK-8177_2.patch, OAK-8177_3.patch
>
>
> 04.03.2019 06:42:46.956 *WARN* 
> [sling-oak-3-org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate-async] 
> org.apache.jackrabbit.oak.composite.CompositeNodeStore Checkpoint 
> f7e6524d-62c4-4589-8137-ca873cec934b doesn't exist
> The above warning was observed - but there are not enough logs around this to 
> identify what's causing this .
>  
> We need to add stack trace when this is logged and probably changed the 
> message to make it unique.
>  
> Also , Since this was logged from a flow in AsyncIndexUpdate - It would make 
> sense to add some more info/ warn level logging there around the code that 
> calls getReferenceCheckpoint()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)