Fix memory leaks » History » Version 1
Jessica Mack, 06/09/2015 06:40 AM
| 1 | 1 | Jessica Mack | h1. Fix memory leaks |
|---|---|---|---|
| 2 | |||
| 3 | h3. Summary |
||
| 4 | |||
| 5 | Ceph has several major memory leaks which should be fixed. |
||
| 6 | |||
| 7 | h3. Owners |
||
| 8 | |||
| 9 | * Name (Affiliation) |
||
| 10 | * Name (Affiliation) |
||
| 11 | * Name |
||
| 12 | |||
| 13 | h3. Interested Parties |
||
| 14 | |||
| 15 | * Danny Al-Gaaf |
||
| 16 | * Haomai Wang |
||
| 17 | |||
| 18 | h3. Current Status |
||
| 19 | |||
| 20 | 0.56.4 is still affected by major memory leaks in osd and (not so badly) monitor. |
||
| 21 | |||
| 22 | h3. Detailed Description |
||
| 23 | |||
| 24 | Ceph has several major memory leaks, even when running without any crashes/ recovery. Fixing these should have a very high priority as this can easily kill whole machines (or crash services due to oom) or even the whole cluster. It should also be documented how users could report memory leak so that devs can fix them. This can include how to start ceph, which options to set so that it produces logs/ dumps which can be analysed. Probably it should also be documented what the expected memory footprint and how the configuration affects memory requirements - like do more osds, monitors, fio/op threads affected memory consumption per monitor/ osd? |
||
| 25 | |||
| 26 | h3. Work items |