You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Currently there is no way in jiva to recognize the reason for late response of IOs from replica.
There could be a network error or an IO delay on filesystem.
What you expected to happen:
Although logs at controller show that there was no response from replica for particular IO, but similar log should be printed in replica also to confirm IO delays from filesystem.
How to reproduce it (as minimally and precisely as possible):
To reproduce the scenario, use slower disks at replica to read/write and pump heavy load. IOs will start timing out due to increased disk pressure.
The text was updated successfully, but these errors were encountered:
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST:
What happened:
Currently there is no way in jiva to recognize the reason for late response of IOs from replica.
There could be a network error or an IO delay on filesystem.
What you expected to happen:
Although logs at controller show that there was no response from replica for particular IO, but similar log should be printed in replica also to confirm IO delays from filesystem.
How to reproduce it (as minimally and precisely as possible):
To reproduce the scenario, use slower disks at replica to read/write and pump heavy load. IOs will start timing out due to increased disk pressure.
The text was updated successfully, but these errors were encountered: