Not autorecovery. But following cases does: 1. Different storage capacity of bookies. 2. Deletions that are not uniform 3. Capacity adds to existing clusters.
On Mon, Oct 10, 2016 at 9:42 PM, Sijie Guo (JIRA) <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/BOOKKEEPER-950? > page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel& > focusedCommentId=15564445#comment-15564445 ] > > Sijie Guo commented on BOOKKEEPER-950: > -------------------------------------- > > I am not sure why auto recovery will cause imbalance. because the > auto-recovery daemon is also a bookkeeper client in theory. > > > Ledger placement policy to accomodate different storage capacity of > bookies > > ------------------------------------------------------------ > --------------- > > > > Key: BOOKKEEPER-950 > > URL: https://issues.apache.org/ > jira/browse/BOOKKEEPER-950 > > Project: Bookkeeper > > Issue Type: New Feature > > Reporter: Rithin Shetty > > Assignee: Rithin Shetty > > Fix For: 4.5.0 > > > > Original Estimate: 672h > > Remaining Estimate: 672h > > > > In our environment, in Salesforce, we are likely to have bookie nodes > with different storage capacity: some will have 1TB others might have 3TB. > Also, our ledgers are likely going to be long lived. The current ledger > placement policy selects the bookies randomly leading to uniform > distribution. This would cause some of bookies to reach high utilization > while the rest would be underutilized. We need a new ledger placement > policy that has higher probability of selecting bookies with higher free > disk space than the ones with lower disk free space. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > -- Jvrao --- First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi
