Erwin Tam commented on ZOOKEEPER-464:
Thanks for the feedback Flavio!
1. Where should I put the summary of the behavior? What about documentation of
this feature? It does require changes to how you set up Bookie Servers (need
to pass in the ZK servers list). Should I put that in comments for this Jira?
Should I upload a text documentation too to describe the feature functionality?
2. I'll add the missing license text. Forgot that I need that for new files.
3. I have a fix for the BufferedChannel issue and it can be done either in the
BufferedChannel code or outside it from the callers. The problem is when it is
created on an existing File. The FileChannels passed to the constructor need
to set their position to the end of the file. Otherwise, the write buffer's
start position will default to 0, the start of the file. That screws things up
when you try to read from it. This bug should already exist if you start up
the Bookies with already existing entry logs and you try to read entries from
there. I don't think there are any unit tests that test that specifically.
> Need procedure to garbage collect ledgers
> Key: ZOOKEEPER-464
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-464
> Project: Zookeeper
> Issue Type: New Feature
> Components: contrib-bookkeeper
> Reporter: Flavio Paiva Junqueira
> Assignee: Erwin Tam
> Fix For: 3.4.0
> Attachments: ZOOKEEPER-464.patch
> An application using BookKeeper is likely to use a large number of ledgers
> over time. Such an application might not need all ledgers created over time
> and might want to delete some of these ledgers to free up some space on
> bookies. The idea of this jira is to implement a procedure that enables an
> application to garbage-collect unwanted ledgers.
> To garbage-collect a ledger, we need to delete the ledger metadata on
> ZooKeeper, and delete the ledger data on corresponding bookies.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.