[jira] [Updated] (OAK-1451) Expose index size

2015-07-22 Thread Michael Marth (JIRA)

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

Michael Marth updated OAK-1451:
---
Fix Version/s: (was: 1.3.4)
   1.3.6

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, tooling
 Fix For: 1.3.6


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-07-20 Thread Davide Giannella (JIRA)

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

Davide Giannella updated OAK-1451:
--
Fix Version/s: (was: 1.3.3)
   1.3.4

Bulk move to 1.3.4

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, tooling
 Fix For: 1.3.4


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-07-01 Thread Davide Giannella (JIRA)

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

Davide Giannella updated OAK-1451:
--
Fix Version/s: (was: 1.3.2)
   1.3.3

Bulk move to 1.3.3.

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, tooling
 Fix For: 1.3.3


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-06-22 Thread Davide Giannella (JIRA)

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

Davide Giannella updated OAK-1451:
--
Fix Version/s: (was: 1.3.1)
   1.3.2

Bulk move to 1.3.2

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, tooling
 Fix For: 1.3.2


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-06-08 Thread Davide Giannella (JIRA)

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

Davide Giannella updated OAK-1451:
--
Fix Version/s: (was: 1.3.0)
   1.3.1

Bulk move to 1.3.1

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, tooling
 Fix For: 1.3.1


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-04-29 Thread Michael Marth (JIRA)

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

Michael Marth updated OAK-1451:
---
Labels: production tooling  (was: production resilience)

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, tooling
 Fix For: 1.3.0


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-03-11 Thread angela (JIRA)

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

angela updated OAK-1451:

Fix Version/s: (was: 1.3.1)
   1.3.0

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, resilience
 Fix For: 1.3.0


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-03-10 Thread Michael Marth (JIRA)

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

Michael Marth updated OAK-1451:
---
Fix Version/s: (was: 1.2)
   1.3.1

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, resilience
 Fix For: 1.3.1


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2015-03-09 Thread Alex Parvulescu (JIRA)

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

Alex Parvulescu updated OAK-1451:
-
Assignee: (was: Alex Parvulescu)

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Priority: Minor
  Labels: production, resilience
 Fix For: 1.2


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2014-10-08 Thread Marcel Reutegger (JIRA)

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

Marcel Reutegger updated OAK-1451:
--
Fix Version/s: (was: 1.1.1)
   1.2

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Assignee: Alex Parvulescu
Priority: Minor
  Labels: production, resilience
 Fix For: 1.2


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2014-09-30 Thread Amit Jain (JIRA)

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

Amit Jain updated OAK-1451:
---
Fix Version/s: (was: 1.1)
   1.1.1

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Assignee: Alex Parvulescu
Priority: Minor
  Labels: production, resilience
 Fix For: 1.1.1


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



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


[jira] [Updated] (OAK-1451) Expose index size

2014-03-31 Thread Alex Parvulescu (JIRA)

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

Alex Parvulescu updated OAK-1451:
-

Fix Version/s: (was: 0.20)
   1.1

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Assignee: Alex Parvulescu
Priority: Minor
  Labels: production, resilience
 Fix For: 1.1


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (OAK-1451) Expose index size

2014-03-18 Thread Michael Marth (JIRA)

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

Michael Marth updated OAK-1451:
---

Fix Version/s: (was: 1.0)
   0.20

 Expose index size
 -

 Key: OAK-1451
 URL: https://issues.apache.org/jira/browse/OAK-1451
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: query
Reporter: Michael Marth
Assignee: Alex Parvulescu
Priority: Minor
  Labels: production, resilience
 Fix For: 0.20


 At the moment some MK's disc needs are largely from the indexes. Maybe we can 
 do something about this, but in the meantime it would be helpful if we could 
 expose the index sizes (num of indexed nodes) via JMX so that they could be 
 easily monitored.
 This would also be helpful to see at which point an index becomes useless (if 
 the majority of content nodes are indexed one might as well not have an index)



--
This message was sent by Atlassian JIRA
(v6.2#6252)