Bug 1067235 - [RFE] Upgrade leveldb to 1.15.0
Summary: [RFE] Upgrade leveldb to 1.15.0
Keywords:
Status: CLOSED DUPLICATE of bug 1306611
Alias: None
Product: Fedora
Classification: Fedora
Component: leveldb
Version: rawhide
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-20 01:06 UTC by Kyle VanderBeek
Modified: 2016-02-11 15:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-11 15:21:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Kyle VanderBeek 2014-02-20 01:06:54 UTC 
Upstream has several fixes and improvements that are fairly critical, including data corruption bugs. We should update to 1.16 for EPEL6 and Fedora.

Notably for my use case, 1.13 fixes a bug on clamping max_open_files which I believe is causing my processes to consume thousands of file handles and causing crashes on a large DB.

There is a rather large set of bug fixes: https://code.google.com/p/leveldb/source/list
Comment 1 Kyle VanderBeek 2014-02-21 00:52:14 UTC 
FYI: Since our need was urgent, I rolled a custom RPM for my local repo using the existing spec. I updated to 1.15.0 and disabled Patch 2, which seems to have made its way upstream (or at least some sort of reasonable facsimile thereof).

It is working fine, and does solve our problem of file handle exhaustion. We were crashing on thousands of open file handles with the broken max_open_files clamping they fixed in 1.13.0.

I'm not 100% certain about the Patch 2 status since I'm not a cross-platform expert, so someone more in the know should verify its status.
Comment 2 Ken Dreyer 2014-03-01 04:15:19 UTC 
Marking as RFE/FutureFeature so this doesn't get auto-closed.
Comment 3 Ruben Kerkhof 2014-08-06 10:58:09 UTC 
Peter, I need leveldb 1.15.0 as well, is there anything I can do to help?
Comment 4 Raphael Groner 2016-02-11 15:21:52 UTC 

*** This bug has been marked as a duplicate of bug 1306611 ***
Note You need to log in before you can comment on or make changes to this bug.