Back to bug 2021738
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2021-11-10 05:27:41 UTC | Link ID | Red Hat Issue Tracker RHCEPH-2226 | |
| Neha Ojha | 2021-11-12 01:17:45 UTC | Assignee | nojha | ksirivad |
| Status | NEW | ASSIGNED | ||
| Veera Raghava Reddy | 2021-11-13 08:10:22 UTC | CC | vereddy | |
| Vikhyat Umrao | 2021-11-15 23:47:27 UTC | Target Release | 5.2 | 5.1 |
| Gaurav Sitlani | 2021-11-18 18:16:39 UTC | CC | gsitlani | |
| Vikhyat Umrao | 2021-11-19 17:58:14 UTC | Summary | [RADOS] New pools created post upgrade being created with "scale-up" profile instead of default "scale-down" in 5.1 | [RADOS] Have default autoscaler profile as scale-up in RHCS 5.1 |
| Neha Ojha | 2021-11-19 18:30:28 UTC | Link ID | Ceph Project Bug Tracker 53309 | |
| Neha Ojha | 2021-11-24 18:13:48 UTC | Link ID | Github ceph/ceph/pull/44032 | |
| Neha Ojha | 2021-12-01 18:26:35 UTC | Status | ASSIGNED | POST |
| Vikhyat Umrao | 2021-12-07 17:17:07 UTC | Link ID | Ceph Project Bug Tracker 53348 | |
| Keywords | Rebase | |||
| errata-xmlrpc | 2021-12-14 17:45:42 UTC | CC | tserlin | |
| Status | POST | MODIFIED | ||
| Fixed In Version | ceph-16.2.7-4.el8cp | |||
| Status | MODIFIED | ON_QA | ||
| Pawan | 2021-12-16 05:02:27 UTC | Status | ON_QA | VERIFIED |
| Aron Gunn | 2022-01-20 22:39:58 UTC | Blocks | 2031073 | |
| CC | agunn | |||
| Aron Gunn | 2022-01-26 21:15:05 UTC | Flags | needinfo?(ksirivad) | |
| Docs Contact | agunn | |||
| Kamoltat (Junior) Sirivadhna | 2022-01-27 04:49:37 UTC | Doc Type | If docs needed, set a value | Release Note |
| Doc Text | The autoscaler is back to a `scale-up` profile by default, where it starts out each pool with minimal PGs and scales up PGs when there is more usage in each pool. However, it also has a `scale-down` profile, where each pool starts out with a full complements of PGs and only scales down when the usage ratio across the pools is not even. With only the `scale-down` profile, the autoscaler identifies any overlapping roots and prevents the pools with such roots from scaling because overlapping roots can cause problems with the scaling process. |
|||
| Kamoltat (Junior) Sirivadhna | 2022-01-27 04:53:35 UTC | Flags | needinfo?(ksirivad) | |
| Aron Gunn | 2022-01-27 16:52:26 UTC | Doc Type | Release Note | Bug Fix |
| Ranjini M N | 2022-02-16 07:27:32 UTC | Flags | needinfo?(ksirivad) | |
| Doc Text | The autoscaler is back to a `scale-up` profile by default, where it starts out each pool with minimal PGs and scales up PGs when there is more usage in each pool. However, it also has a `scale-down` profile, where each pool starts out with a full complements of PGs and only scales down when the usage ratio across the pools is not even. With only the `scale-down` profile, the autoscaler identifies any overlapping roots and prevents the pools with such roots from scaling because overlapping roots can cause problems with the scaling process. | .The autoscaler is set to scale-up by default in {storage-product} 5.1 With this release, the autoscaler is set to scale-up by default where it starts out each pool with minimal placement groups (PGs) and scales up PGs when there is more usage in each pool. There is also a scale-down profile, where each pool starts with compliments of PGS and only scales down when the usage ratio across the pools is not even. In a scale-down profile, the autoscaler identifies any overlapping roots and prevents the pools with such roots from scaling because overlapping roots can cause problems with the scaling process. | ||
| CC | rmandyam | |||
| Kamoltat (Junior) Sirivadhna | 2022-02-16 15:06:00 UTC | Flags | needinfo?(ksirivad) | |
| Ranjini M N | 2022-02-17 07:43:08 UTC | Doc Text | .The autoscaler is set to scale-up by default in {storage-product} 5.1 With this release, the autoscaler is set to scale-up by default where it starts out each pool with minimal placement groups (PGs) and scales up PGs when there is more usage in each pool. There is also a scale-down profile, where each pool starts with compliments of PGS and only scales down when the usage ratio across the pools is not even. In a scale-down profile, the autoscaler identifies any overlapping roots and prevents the pools with such roots from scaling because overlapping roots can cause problems with the scaling process. | .The autoscaler is set to scale-up by default in {storage-product} 5.1 With this release, the autoscaler is set to scale-up by default where it starts out each pool with minimal placement groups (PGs) and scales up PGs when there is more usage in each pool. There is also a scale-down profile, where each pool starts with ideal full-capacity PGs and only scales down when the usage ratio across the pools is not even. In a scale-down profile, the autoscaler identifies any overlapping roots and prevents the pools with such roots from scaling because overlapping roots can cause problems with the scaling process. |
| Aron Gunn | 2022-02-21 17:42:23 UTC | Docs Contact | agunn | rmandyam |
| errata-xmlrpc | 2022-04-04 08:03:29 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-04-04 10:22:28 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-04-04 10:22:28 UTC | |||
| errata-xmlrpc | 2022-04-04 10:22:45 UTC | Link ID | Red Hat Product Errata RHSA-2022:1174 |
Back to bug 2021738