-
Notifications
You must be signed in to change notification settings - Fork 123
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
No operations per second #44
Comments
Update: |
Hi @hansbogert, this should not happens since the JS routine to render the page is called every 5 seconds by default. Can you tell me which version of ceph you are using and can you provide the output of
Regards, |
I also just changed something in the JS code regarding the changed json structure in the jewel release. Can you pull the latest code and check if the problem is still there? |
Hi @hansbogert thanks for the infos! I probably found the error. Can you pull the latest code and try again? Cheers, |
Seems to do the trick. Now updates correctly from a 1-cell row "operations / second" to a 2-cell row with "write ops / second" and "read ops / second". |
You mean the "write ops" field stays at "5"? it is normal that ceph reports iops after write/reads are only done, but only one or two seconds. |
Yeah this stays indefinitely if there isn’t any ops or byte transfer afterwards.
… On Jan 10, 2017, at 11:56 AM, Christian Eichelmann ***@***.***> wrote:
You mean the "write ops" field stays at "5"? it is normal that ceph reports iops after write/reads are only done, but only one or two seconds.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACgk9BuC0iW08fJOOUB9AmV-ZFgBh7PVks5rQ2POgaJpZM4Ka5Bc>.
|
Ok, i've checked the whole code again with a mocked ceph backend. It works for me now. Can you pull the latest code and give it a try again? |
Awesome! |
In the screenshots of the README.md we can see the operations-per-second metric. Is it expected that this metric can't be seen in a default deployment?
The text was updated successfully, but these errors were encountered: