[jira] [Commented] (IGNITE-7951) Add metrics for remains to evict keys/partitions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715399#comment-16715399
 ] 

ASF GitHub Bot commented on IGNITE-7951:


Github user alex-plekhanov closed the pull request at:

https://github.com/apache/ignite/pull/4055


> Add metrics for remains to evict keys/partitions
> 
>
> Key: IGNITE-7951
> URL: https://issues.apache.org/jira/browse/IGNITE-7951
> Project: Ignite
>  Issue Type: New Feature
>  Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: jmx
> Fix For: 2.7
>
>
> Need to add some metrics for remains to evict keys/partitions to indicate 
> total amount of evicting work. In some cases we have synchronous eviction and 
> it's critically important to know how many keys need to be evicted before 
> exchange process end and cluster became working again. In some other cases we 
> just wanna know what happens in cluster now (background eviction without 
> workload) and when cluster will became 100% healthy. 



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

[jira] [Commented] (IGNITE-7951) Add metrics for remains to evict keys/partitions

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487428#comment-16487428
 ] 

ASF GitHub Bot commented on IGNITE-7951:


GitHub user alex-plekhanov opened a pull request:

https://github.com/apache/ignite/pull/4055

IGNITE-7951 Add metrics for remains to evict keys/partitions



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alex-plekhanov/ignite ignite-7951

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4055.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4055


commit 8d21d5713f3ea326d252ae3dd13adb890102d8a9
Author: Aleksey Plekhanov 
Date:   2018-05-23T15:05:54Z

IGNITE-7951 Add metrics for remains to evict keys/partitions




> Add metrics for remains to evict keys/partitions
> 
>
> Key: IGNITE-7951
> URL: https://issues.apache.org/jira/browse/IGNITE-7951
> Project: Ignite
>  Issue Type: New Feature
>  Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Labels: jmx
> Fix For: 2.6
>
>
> Need to add some metrics for remains to evict keys/partitions to indicate 
> total amount of evicting work. In some cases we have synchronous eviction and 
> it's critically important to know how many keys need to be evicted before 
> exchange process end and cluster became working again. In some other cases we 
> just wanna know what happens in cluster now (background eviction without 
> workload) and when cluster will became 100% healthy. 



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

[jira] [Commented] (IGNITE-7951) Add metrics for remains to evict keys/partitions

[Aleksey Plekhanov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482900#comment-16482900
 ] 

Aleksey Plekhanov commented on IGNITE-7951:
---

I want to clarify: this ticket is about keys left to evict in RENTING 
partitions after rebalance complete, and RENTING partitions count. It's not 
related in any way to page eviction, so I removed the link to ticket about page 
eviction rate to avoid confusion.

> Add metrics for remains to evict keys/partitions
> 
>
> Key: IGNITE-7951
> URL: https://issues.apache.org/jira/browse/IGNITE-7951
> Project: Ignite
>  Issue Type: New Feature
>  Components: general
>Affects Versions: 2.4
>Reporter: Alexander Belyak
>Assignee: Aleksey Plekhanov
>Priority: Major
>
> Need to add some metrics for remains to evict keys/partitions to indicate 
> total amount of evicting work. In some cases we have synchronous eviction and 
> it's critically important to know how many keys need to be evicted before 
> exchange process end and cluster became working again. In some other cases we 
> just wanna know what happens in cluster now (background eviction without 
> workload) and when cluster will became 100% healthy. 



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