empiredan opened a new issue, #2061:
URL: https://github.com/apache/incubator-pegasus/issues/2061

   The block cache has always been set to 24GB, and the metric value observed 
in monitoring system is also 24GB. However, after Pegasus is upgraded from 2.0 
to 2.4, the metric value becomes incorrect.
   
   As is shown in the following graph, the left side is the usage of the block 
cache before the upgrade, which is correct value; the right side is the usage 
after the upgrade, which is always 0 and incorrect:
   
![image](https://github.com/apache/incubator-pegasus/assets/743379/5ad8caa3-086b-435f-b3e3-c94b42e6f744)
   
   The following graph is the usage of physical memory with the time 
corresponding to the above graph, which is correct:
   
![image](https://github.com/apache/incubator-pegasus/assets/743379/1309cf2d-17af-4aa6-bd1a-2e6c52840aa1)
   
   It's obvious that the replica server has been started and the block cache 
usage should has become 24GB, which is still
   actually 0.
   
   Then, restart the replica servers and their usage of block cache become 
non-zero values; however, After a short while
   , the growth stopped and  it stayed at a fixed value forever which is 
incorrect:
   
![image](https://github.com/apache/incubator-pegasus/assets/743379/ec7badfe-858c-4d75-9325-24de95265565)
   
   Similarly, the following graph is the usage of physical memory with the time 
corresponding to the above graph, which is also correct:
   
![image](https://github.com/apache/incubator-pegasus/assets/743379/b63e30c8-5dd7-4049-86db-df04120bae03)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to