[jira] [Updated] (OAK-3054) IndexStatsMBean should provide some details if the async indexing is failing

2015-08-23 Thread Amit Jain (JIRA)

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

Amit Jain updated OAK-3054:
---
Fix Version/s: (was: 1.2.4)
   1.2.5

> IndexStatsMBean should provide some details if the async indexing is failing
> 
>
> Key: OAK-3054
> URL: https://issues.apache.org/jira/browse/OAK-3054
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Reporter: Chetan Mehrotra
>Priority: Minor
>  Labels: resilience, tooling
> Fix For: 1.3.5, 1.2.5
>
>
> If the background indexing fails for some reason it logs the exception for 
> the first time then it logs the exception like _The index update failed ..._. 
> After that if indexing continues to fail then no further logging is done so 
> as to avoid creating noise.
> This poses a problem on long running system where original exception might 
> not be noticed and index does not show updated result. For such cases we 
> should expose the indexing health as part of {{IndexStatsMBean}}. Also we can 
> provide the last recorded exception. 
> Administrator can then check for MBean and enable debug logs for further 
> troubleshooting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3133) Make compaction map more efficient for offline compaction

2015-08-23 Thread Amit Jain (JIRA)

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

Amit Jain updated OAK-3133:
---
Fix Version/s: (was: 1.2.4)
   1.2.5

> Make compaction map more efficient for offline compaction
> -
>
> Key: OAK-3133
> URL: https://issues.apache.org/jira/browse/OAK-3133
> Project: Jackrabbit Oak
>  Issue Type: Sub-task
>  Components: run
>Reporter: Michael Dürig
>Assignee: Francesco Mari
>  Labels: compaction, gc
> Fix For: 1.3.5, 1.0.20, 1.2.5
>
> Attachments: OAK-3133-01.patch
>
>
> The compaction map might be expensive. See OAK-2862 for the analysis. We 
> should find ways to lower the impact of this on offline compaction. One 
> option would be to make the compress cycle configurable, which would require 
> more heap. Another option would be to leverage the persisted compaction map 
> here also.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (OAK-3176) Provide an option to include a configured boost query while searching

2015-08-23 Thread Amit Jain (JIRA)

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

Amit Jain updated OAK-3176:
---
Fix Version/s: (was: 1.2.4)
   1.2.5

> Provide an option to include a configured boost query while searching
> -
>
> Key: OAK-3176
> URL: https://issues.apache.org/jira/browse/OAK-3176
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: solr
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 1.3.5, 1.2.5
>
>
> For tweaking relevancy it's sometimes useful to include a boost query that 
> gets applied at query time and modifies the ranking accordingly.
> This can be done also by setting it by hand as a default parameter to the 
> /select request handler, but for convenience it'd be good if the Solr 
> instance configuration files wouldn't be touched.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)