Hello @rzarzyns ,
If you look back at C2, you will see that the error is indeed from the cluster log, ceph.log. Also, given the very ephemeral nature of the problem, maybe a small code change to log something more at a regular logging level when this issue is triggered would be the best action here.
Actions:
Me: Explain issue and get the case closed
Me: Write a KCS to help others
ENG: Make code change so more data is logged when this issue occurs enabling better understanding in future releases
Let me know what you think, thank you!
Best regards,
Manny
Hello @rzarzyns ,
If you look back at C2, you will see that the error is indeed from the cluster log, ceph.log. Also, given the very ephemeral nature of the problem, maybe a small code change to log something more at a regular logging level when this issue is triggered would be the best action here.
Actions:
Me: Explain issue and get the case closed
Me: Write a KCS to help others
ENG: Make code change so more data is logged when this issue occurs enabling better understanding in future releases
Let me know what you think, thank you!
Best regards,
Manny