Yup. I would backport BOOKKEEPER-438 to 4.3.2. - Sijie
On Fri, Nov 6, 2015 at 12:23 AM, Enrico Olivelli - Diennea < [email protected]> wrote: > I’m running 4.3.1 in production. So I think that there is no hope nowadays > > > > In https://issues.apache.org/jira/browse/BOOKKEEPER-878 you say you will > port –BOOKKEEPER-438 to 4.3.2, is it correct ? > > Actually I’m waiting for 4.3.2 for another problem, it would be very > helpful to include BOOKKEEPER-438 > > > > if you think that it is doable I would reproduce the env in staging > machines by creating 100.000 ledgers and I will try to upgrade otherwise I > do not known how to recover my production system (with 800.000 ledgers) > > > > Thank you very much > > > > *Da:* Sijie Guo [mailto:[email protected]] > *Inviato:* giovedì 5 novembre 2015 19:57 > *A:* [email protected] > *Oggetto:* Re: switching from FlatLedgerManager to > HierarchicalLedgerManager > > > > It isn't doable in 4.3.* version. since the id generation path isn't > configurable in HierarchicalLedgerManager. It is doable after we have > https://issues.apache.org/jira/browse/BOOKKEEPER-438 in master. > > created a jira about verifying and documenting the steps: > https://issues.apache.org/jira/browse/BOOKKEEPER-878. I will try to get > to it today. Enrico, does it work for you? > > - Sijie > > > > On Wed, Nov 4, 2015 at 8:07 PM, Enrico Olivelli - Diennea < > [email protected]> wrote: > > Hi, > > I need to switch from FlatLedgerManager to HierarchicalLedgerManager in a > production system. > > What is the best procedure ? > > Is it possible to migrate existing ledgers ? > > > > http://bookkeeper.apache.org/docs/master/bookkeeperInternals.html > > > > Thanks > > > > -- Enrico > > > > ------------------------------ > Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed > email marketing! http://www.magnews.it/newsletter/ > > The information in this email is confidential and may be legally > privileged. If you are not the intended recipient please notify the sender > immediately and destroy this email. Any unauthorized, direct or indirect, > disclosure, copying, storage, distribution or other use is strictly > forbidden. >
