Re: Right MXBean for new metrics

Ok, I will rename the metrics. 2017-11-24 22:55 GMT+03:00 Dmitriy Setrakyan : > Got it, but I do not like the name of the metric, I think it is confusing. > > I would provide the following metrics: > - minNumberOfCopies() > - maxNumberOfCopies() > > Will this work for you?

Re: Right MXBean for new metrics

Got it, but I do not like the name of the metric, I think it is confusing. I would provide the following metrics: - minNumberOfCopies() - maxNumberOfCopies() Will this work for you? D. On Thu, Nov 23, 2017 at 10:38 PM, Alex Plehanov wrote: > We have target redundancy

Re: Right MXBean for new metrics

We have target redundancy level - 4. If, for some reason, minimal redundancy level reached the value of 1, then each next node left the cluster may cause data loss or service unavailability. 2017-11-24 1:31 GMT+03:00 Dmitriy Setrakyan : > Alex, > > I am really confused.

Re: Right MXBean for new metrics

Alex, I am really confused. What do you need to know the "minimal partition redundancy" for? What will it give you? D. On Thu, Nov 23, 2017 at 2:25 PM, Alex Plehanov wrote: > Example was in my previous letters: if we have in our cluster for cache > group one partition

Re: Right MXBean for new metrics

Example was in my previous letters: if we have in our cluster for cache group one partition with 2 copies (1 primary and 1 backup) and other partitions with 4 copies (1 primary and 3 backups), then minimal partition redundancy level for this cache group will be 2. Maybe code will be more clear

Re: Right MXBean for new metrics

I think you are talking about the case when cluster temporarily gets into unbalanced state and needs to rebalance. However, I am still not sure what this metric would show. Can you provide an example? D. On Wed, Nov 22, 2017 at 2:10 PM, Alex Plehanov wrote: > It's not

Re: Right MXBean for new metrics

It's not about caches. Each partition has certain amount of copies. Amount of copies may differ for different partitions of one cache group. This configuration possible: 1) With custom affinity function 2) When nodes left the cluster, till rebalancing is not finished 2017-11-23 0:18 GMT+03:00

Re: Right MXBean for new metrics

On Wed, Nov 22, 2017 at 12:39 PM, Alex Plehanov wrote: > Hello Dmitriy, > > I agree. > > By "minimal partition redundancy level for cache group" I mean minimal > number of partition copies among all partitions of this cache group. > For example, if we have in our cluster

Re: Right MXBean for new metrics

Hello Dmitriy, I agree. By "minimal partition redundancy level for cache group" I mean minimal number of partition copies among all partitions of this cache group. For example, if we have in our cluster for cache group one partition with 2 copies (1 primary and 1 backup) and other partitions

Re: Right MXBean for new metrics

Hi Alex, I think the proper approach would be to have a separate MBean for cache groups. It should show average metrics across all the caches in the group and some additional metrics as well. Agree? Also, I am not sure I understand what is "partition redundancy level" and what that metric would

Right MXBean for new metrics

Hello, Igniters! I would like to discuss the implementation of ticket IGNITE-6871. In our Ignite instance there are more than 1000 caches and about 10 cache groups. To minimize the probability of data loss we need to alert when a critical level of redundancy in cluster is reached. So, we