[
https://issues.apache.org/jira/browse/BOOKKEEPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171016#comment-13171016
]
Hudson commented on BOOKKEEPER-141:
-----------------------------------
Integrated in bookkeeper-trunk #283 (See
[https://builds.apache.org/job/bookkeeper-trunk/283/])
BOOKKEEPER-141: Run extracting ledger id from entry log files in GC thread
to speed up bookie restart (Sijie Gou via ivank)
ivank :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/EntryLogger.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/EntryLogTest.java
> Run extracting ledger id from entry log files in GC thread to speed up bookie
> restart
> -------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-141
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-141
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Affects Versions: 4.0.0
> Reporter: Sijie Guo
> Assignee: Ivan Kelly
> Fix For: 4.1.0
>
> Attachments: BOOKKEEPER-141.patch
>
>
> Currently bookie server do extracting ledger id from entry log files when
> creating a new entry log.
> When we have lots of entry logs, we have to scan all these entry log files,
> then bookie server will be blocked until finished extraction.
> But it is not necessary. Since extraction is only for garbage collection, we
> can do extraction in GC thread before gc entry log files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
