Jenkins build is still unstable: bookkeeper-trunk #750
See https://builds.apache.org/job/bookkeeper-trunk/750/
[jira] [Updated] (BOOKKEEPER-430) Remove manual bookie registration from overview
[ https://issues.apache.org/jira/browse/BOOKKEEPER-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated BOOKKEEPER-430: Attachment: BOOKKEEPER-430.patch Remove manual bookie registration from overview --- Key: BOOKKEEPER-430 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-430 Project: Bookkeeper Issue Type: Improvement Affects Versions: 4.1.0 Reporter: Flavio Junqueira Assignee: Flavio Junqueira Attachments: BOOKKEEPER-430.patch The documentation suggests that a user needs to manually register a bookie, which is not right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BOOKKEEPER-430) Remove manual bookie registration from overview
[ https://issues.apache.org/jira/browse/BOOKKEEPER-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Junqueira updated BOOKKEEPER-430: Component/s: Documentation Remove manual bookie registration from overview --- Key: BOOKKEEPER-430 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-430 Project: Bookkeeper Issue Type: Improvement Components: Documentation Affects Versions: 4.1.0 Reporter: Flavio Junqueira Assignee: Flavio Junqueira Attachments: BOOKKEEPER-430.patch The documentation suggests that a user needs to manually register a bookie, which is not right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BOOKKEEPER-431) Duplicate definition of COOKIES_NODE
[ https://issues.apache.org/jira/browse/BOOKKEEPER-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475113#comment-13475113 ] Flavio Junqueira commented on BOOKKEEPER-431: - Yeah, I'd rather have the constants in one single place. COOKIE_NODE was introduced in BOOKKEEPER-263, but before that we had BOOKIE_COOKIE_PATH, so I'm not entirely sure what the history of duplication is. Ivan, Sijie, do you guys have any other insight to add here? Duplicate definition of COOKIES_NODE Key: BOOKKEEPER-431 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-431 Project: Bookkeeper Issue Type: Improvement Affects Versions: 4.1.0 Reporter: Flavio Junqueira Assignee: Uma Maheswara Rao G Priority: Minor Fix For: 4.2.0 Is it necessary two definitions of COOKIES_NODE, one in cookie.java and one in AbstractZkLedgerManager? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (BOOKKEEPER-432) Improve performance of entry log range read per ledger entries
Yixue (Andrew) Zhu created BOOKKEEPER-432: - Summary: Improve performance of entry log range read per ledger entries Key: BOOKKEEPER-432 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-432 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-server Affects Versions: 4.1.0 Environment: Linux Reporter: Yixue (Andrew) Zhu We observed random I/O reads when some subscribers fall behind (on some topics), as delivery needs to scan the entry logs (thru ledger index), which are interleaved with ledger entries across all ledgers being served. Essentially, the ledger index is a non-clustered index. It is not effective when a large number of ledger entries need to be served, which tend to be scattered around due to interleaving. Some possible improvements: 1. Change the ledger entries buffer to use a SkipList (or other suitable), sorted on (ledger, entry sequence). When the buffer is flushed, the entry log is written out in the already-sorted order. The active ledger index can point to the entries buffer (SkipList), and fixed up with entry-log position once latter is persisted. Or, the ledger index can be just rebuilt on demand. The entry log file tail can have index attached (light-weight b-tree, similar with big-table). We need to track per ledger which log files contribute entries to it, so that in-memory index can be rebuilt from the tails of corresponding log files. 2. Use affinity concept to make ensembles of ledgers (belonging to same topic) as identical as possible. This will help above 1. be more effective. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BOOKKEEPER-432) Improve performance of entry log range read per ledger entries
[ https://issues.apache.org/jira/browse/BOOKKEEPER-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yixue (Andrew) Zhu updated BOOKKEEPER-432: -- Affects Version/s: (was: 4.1.0) 4.2.0 Improve performance of entry log range read per ledger entries --- Key: BOOKKEEPER-432 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-432 Project: Bookkeeper Issue Type: Improvement Components: bookkeeper-server Affects Versions: 4.2.0 Environment: Linux Reporter: Yixue (Andrew) Zhu Labels: patch We observed random I/O reads when some subscribers fall behind (on some topics), as delivery needs to scan the entry logs (thru ledger index), which are interleaved with ledger entries across all ledgers being served. Essentially, the ledger index is a non-clustered index. It is not effective when a large number of ledger entries need to be served, which tend to be scattered around due to interleaving. Some possible improvements: 1. Change the ledger entries buffer to use a SkipList (or other suitable), sorted on (ledger, entry sequence). When the buffer is flushed, the entry log is written out in the already-sorted order. The active ledger index can point to the entries buffer (SkipList), and fixed up with entry-log position once latter is persisted. Or, the ledger index can be just rebuilt on demand. The entry log file tail can have index attached (light-weight b-tree, similar with big-table). We need to track per ledger which log files contribute entries to it, so that in-memory index can be rebuilt from the tails of corresponding log files. 2. Use affinity concept to make ensembles of ledgers (belonging to same topic) as identical as possible. This will help above 1. be more effective. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
