| Summary: | [RFE] MongoDB 3 with Red Hat OpenStack | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Chaitanya Shastri <cshastri> |
| Component: | mongodb | Assignee: | hguemar |
| Status: | CLOSED WONTFIX | QA Contact: | Shai Revivo <srevivo> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | cshastri, ealcaniz, egafford, fbaudin, fpercoco, pkilambi, skinjo, srevivo |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-18 14:26:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Chaitanya Shastri
2016-08-17 12:04:50 UTC
(In reply to cshastri from comment #0) > Description of problem: > With OSP 8 and OSP 9, we ship MongoDB version 2.6.11 which uses MMAPv1 as > storage engine. The problem with this storage engine is that it does not > return free space to the file system and has a lengthy procedure to reclaim > the space. > > MongoDB version 3.0 and above has WiredTiger as a default storage engine and > this version overcomes the space issue. > > Is there a specific reason that we do not include MongoDB version 3.0 in Red > Hat OpenStack? > > Do we have a timeline as to when it will be included? We don't have a timeline and there has not been a need to upgrade it till now. I don't believe we're testing mongodb 3.0 in the upstream gate so I'd be very reluctant to upgrading our mongodb version. Any specific reason why the customer is requesting this other than the space MMAPv1 seems to be taking on disk? Hi Flavio,
>Any specific reason why the customer is requesting this other than the space MMAPv1 seems to be taking on disk?
No. The ceilometer TTL seems to be working fine. But the only issue is that it is a long procedure to reclaim the space that was used by ceilometer database.
(In reply to cshastri from comment #4) > Hi Flavio, > > >Any specific reason why the customer is requesting this other than the space MMAPv1 seems to be taking on disk? > > No. The ceilometer TTL seems to be working fine. But the only issue is that > it is a long procedure to reclaim the space that was used by ceilometer > database. Yes, I know there are two new KCS to shrink DBs https://access.redhat.com/solutions/2531821 https://access.redhat.com/solutions/2497621 Yes, we are looking target to OSP10/11 if possible or use gnocchi instead MongoDB for Ceilometer. Moving back to DFG:Telemetry per conversation with Franck. *** Bug 1279325 has been marked as a duplicate of this bug. *** |