If it uses PriorityQueue <https://en.wikipedia.org/wiki/Priority_queue#:~:text=In%20computer%20science%2C%20a%20priority,an%20element%20with%20low%20priority.> Data Structure an element with high priority should be dequeued before an element with low priority. On Wed, Dec 2, 2020 at 7:32 PM Seena Fallah <seenafallah@gmail.com> wrote:
"Higher recovery priority might cause performance degradation until recovery completes." But what about this statement? I found this that it means if I set priority to 63, I will lose the cluster performance for clients. Am I wrong? Does it mean the performance for recovery?
[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/1.3/html/... Can you please point me to the correct section. I don't find the point of
I'm using nautilus 14.2.14. this doc.
On Wed, Dec 2, 2020 at 7:04 PM Peter Lieven <pl@kamp.de> wrote:
Am 02.12.20 um 15:04 schrieb Seena Fallah:
I don't think so! I want to slow down the recovery not speed up and it says I should reduce these values.
I read the documentation the same. Low value = low weight, High value = high weight. [1]
Operations with higher weight get easier dispatched.
May I ask which exact issue are you seeing and which ceph version are you using?
Peter
[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/1.3/html/...