[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-3495:
Labels: IEP-35 iep-6 (was: iep-6)
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis A. Magda
>Priority: Major
> Labels: IEP-35, iep-6
> Fix For: 3.0
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-3495:
---
Fix Version/s: (was: 2.8)
3.0
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis A. Magda
>Priority: Major
> Labels: iep-6
> Fix For: 3.0
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-3495:
-
Fix Version/s: (was: 2.7)
2.8
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: iep-6
> Fix For: 2.8
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-3495:
---
Fix Version/s: (was: 2.6)
2.7
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: iep-6
> Fix For: 2.7
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Setrakyan updated IGNITE-3495:
--
Fix Version/s: 2.6
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Priority: Major
> Labels: iep-6
> Fix For: 2.6
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Labels: iep-6 (was: )
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Priority: Major
> Labels: iep-6
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Labels: (was: iep-6)
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Labels: iep-6 (was: )
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vyacheslav Koptilin
> Labels: iep-6
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-3495:
Fix Version/s: (was: 2.3)
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vyacheslav Koptilin
> Attachments: example-default.xml, ExampleNodeStartupClient.java,
> IGNITE_3495.patch
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3495:
Fix Version/s: (was: 2.1)
2.2
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vyacheslav Koptilin
> Fix For: 2.2
>
> Attachments: example-default.xml, ExampleNodeStartupClient.java,
> IGNITE_3495.patch
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-3495:
Fix Version/s: (was: 2.0)
2.1
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vladislav Pyatkov
> Fix For: 2.1
>
> Attachments: example-default.xml, ExampleNodeStartupClient.java,
> IGNITE_3495.patch
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Affects Version/s: 1.6
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vladislav Pyatkov
> Fix For: 2.0
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Fix Version/s: 2.0
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Vladislav Pyatkov
> Fix For: 2.0
>
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-3495:
--
Attachment: IGNITE_3495.patch
Before create pull request I would appreciate if community group review my
first patch (it must fix the test).
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Vladislav Pyatkov
> Attachments: ExampleNodeStartupClient.java, IGNITE_3495.patch,
> example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Attachment: (was: default-config.xml)
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Velichko
> Attachments: ExampleNodeStartupClient.java, example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Attachment: example-default.xml
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Velichko
> Attachments: ExampleNodeStartupClient.java, example-default.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3495) CacheMetrics.getAverage###Time is not calculated properly
[
https://issues.apache.org/jira/browse/IGNITE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3495:
Attachment: ExampleNodeStartupClient.java
default-config.xml
> CacheMetrics.getAverage###Time is not calculated properly
> -
>
> Key: IGNITE-3495
> URL: https://issues.apache.org/jira/browse/IGNITE-3495
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Velichko
> Attachments: ExampleNodeStartupClient.java, default-config.xml
>
>
> {{CacheMetrics.getAverageGetTime}}, {{CacheMetrics.getAveragePutTime}} and
> {{CacheMetrics.getAverageRemoveTime}} are not calculated properly in the
> following scenario:
> - start a server node;
> - start a client node that will perform gets and puts;
> - {{CacheMetrics.getAverage###Time}} will always be 0 for the server node's
> cluster group.
> The issue happens because {{CacheMetricsImpl.add###TimeNanos}} method is not
> called on the server side when a metric related event happens.
> In the attache you can find source that showcases the bug.
> - start basic {{ExampleNodeStartup}} using attached configuration
> {{example-default.xml}} conjuration;
> - start {{ExampleNodeStartupClient}}. You will see that average metrics are
> not incremented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
