You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by tschauenberg <ts...@invidi.com> on 2020/07/21 22:23:44 UTC
Bug with client cache_size for metrics() and localMetrics()
IgniteClusterClient.java
<http://apache-ignite-users.70518.x6.nabble.com/file/t2920/IgniteClusterClient.java>
IgniteClusterNode1.java
<http://apache-ignite-users.70518.x6.nabble.com/file/t2920/IgniteClusterNode1.java>
IgniteClusterNode2.java
<http://apache-ignite-users.70518.x6.nabble.com/file/t2920/IgniteClusterNode2.java>
The following bug could be reproduced on both server and client nodes with
Ignite 2.7.0. In Ignite 2.8.1, the server node counts are correct but the
client node counts are still incorrect.
*Procedure:*
1. Run attached IgniteClusterNode1.java
2. Run attached IgniteClusterNode2.java
3. Run attached IgniteClusterClient.java
4. Wait for client to put 100 items in the test cache and then observe the
local and cluster wide cache_size metrics
5. The cluster wide metrics should be 100 on both servers and client. The
local metrics on the server should sum to 100 and the client should show 0.
*Summary:
*
* both server and client counts were wrong in Ignite 2.7.0
* server counts were fixed somewhere before Ignite 2.8.1 but client counts
are still wrong
*Ignite 2.7.0 Results:*
*Server1:*
/Actual:/
Server1 - Cluster metrics: cache_size=40
Server1 - Local metrics: cache_size=40
/Expected:/
Server1 - Cluster metrics: cache_size=100
Server1 - Local metrics: cache_size=40
/Working Incorrectly/
*Server2:*
/Actual:/
Server2 - Cluster metrics: cache_size=60
Server2 - Local metrics: cache_size=60
/Expected:/
Server2 - Cluster metrics: cache_size=100
Server2 - Local metrics: cache_size=60
/Working Incorrectly/
*Client:*
/Actual:/
Client - Cluster metrics: cache_size=0
Client - Local metrics: cache_size=0
/Expected:/
Client - Cluster metrics: cache_size=100
Client - Local metrics: cache_size=0
/Working Incorrectly/
*Ignite 2.8.1 Results:*
*Server1:*
/Actual and Expected:/
Server1 - Cluster metrics: cache_size=100
Server1 - Local metrics: cache_size=40
/Working Correctly/
*Server2:*
/Actual and Expected:/
Server2 - Cluster metrics: cache_size=100
Server2 - Local metrics: cache_size=60
/Working Correctly/
*Client:*
/Actual:/
Client - Cluster metrics: cache_size=0
Client - Local metrics: cache_size=0
/Expected:/
Client - Cluster metrics: cache_size=100
Client - Local metrics: cache_size=0
/Working Incorrectly/
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Bug with client cache_size for metrics() and localMetrics()
Posted by tschauenberg <ts...@invidi.com>.
Apologies. I modified the tests to wait longer for the 2.8.1 test scenario
on the client printouts and eventually the cluster metrics started
reporting.
Client - Cluster metrics: cache_size=100
Client - Local metrics: cache_size=0
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/