You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (Created) (JIRA)" <ji...@apache.org> on 2011/12/12 15:34:30 UTC
[jira] [Created] (BOOKKEEPER-141) Run extracting ledger id from
entry log files to speed up bookie restart
Run extracting ledger id from entry log files 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: Sijie Guo
Fix For: 4.1.0
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
[jira] [Updated] (BOOKKEEPER-141) Run extracting ledger id from
entry log files in GC thread to speed up bookie restart
Posted by "Sijie Guo (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sijie Guo updated BOOKKEEPER-141:
---------------------------------
Attachment: BOOKKEEPER-141.patch
> 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: Sijie Guo
> 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
[jira] [Commented] (BOOKKEEPER-141) Run extracting ledger id from
entry log files in GC thread to speed up bookie restart
Posted by "Ivan Kelly (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170989#comment-13170989 ]
Ivan Kelly commented on BOOKKEEPER-141:
---------------------------------------
lgtm +1
> 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: Sijie Guo
> 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
[jira] [Commented] (BOOKKEEPER-141) Run extracting ledger id from
entry log files in GC thread to speed up bookie restart
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (BOOKKEEPER-141) Run extracting ledger id from
entry log files in GC thread to speed up bookie restart
Posted by "Sijie Guo (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sijie Guo updated BOOKKEEPER-141:
---------------------------------
Summary: Run extracting ledger id from entry log files in GC thread to speed up bookie restart (was: Run extracting ledger id from entry log files to speed up bookie restart)
> 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: Sijie Guo
> Fix For: 4.1.0
>
>
> 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