Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Management Console Reporting incorrect values for backups #10454

Closed
sertugkaya opened this issue Apr 27, 2017 · 3 comments
Closed

Management Console Reporting incorrect values for backups #10454

sertugkaya opened this issue Apr 27, 2017 · 3 comments

Comments

@sertugkaya
Copy link

@sertugkaya sertugkaya commented Apr 27, 2017

Given that there is one copy of the data across a Native Map I was expecting to see identical memory footprint on the entry and the backups with identical sum across a server. But it's not the case.
I am running 3.8.1 Dot Net client and 3.8.1 server side on Windows
The same stats on Linux servers shows the Entry memory and Backup Memory correctly with consistent results per server (running 3.8.1).
1st screen shots (2 servers) represents the Windows view: here the total memory entries does not match the total memory backups
2nd screen shot is the home view of that first Map view
3rd screen shot shots the map view of Linux where memory on entries = memory on backups
1:
image001
2:
image002
3:
image003

@sertugkaya
Copy link
Author

@sertugkaya sertugkaya commented Apr 27, 2017

ZD no: 2655

@tkountis
Copy link
Contributor

@tkountis tkountis commented May 10, 2017

Back-ported in 3.8.2 #1462

@tkountis
Copy link
Contributor

@tkountis tkountis commented May 10, 2017

This appears to be a problem with partition migrations, rather than the OS itself. When partitions are cleared due to replication/migration etc, then the size was not cleared, and the new data just added up to the previous value. The fix should mitigate that issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.