I think what Sebastian said is that manual recovery didn't even work. This seems to a bit strange to me. The autorecovery will check if the bookie is available or not. After that, it should rereplicate the data from other nodes in the ensemble. This seems to indicate something is broken. Sebastian, Can you point us some loggings?
Sijie On Nov 19, 2016 9:46 AM, "Rithin Shetty" <[email protected]> wrote: > A few things to note: Make sure 'autoRecoveryDaemonEnabled' set to true on > all the bookie conf files; by default this is false. Otherwise recovery > will not work. The auto recovery process tries to make sure that the data > doesn't exist on the source node before replicating to destination. That > might be the reason why it is trying to talk to the source node. > > --Rithin > > On Fri, Nov 18, 2016 at 12:00 PM, Sebastián Schepens < > [email protected]> wrote: > >> Hi guys, >> I'm running into some issues while trying to recover a decomissioned node. >> Both the recovery command and autorecovery processes fail trying to >> connect to the failing node, which seems reasonable because the node is >> down. >> But I don't get why it's trying to connect to that node, according to the >> documentation it should pull ledger data from other nodes in the ensemble >> (3) and replicate them. >> The recovery command also seems to completely ignore the destination node >> given as third argument. >> >> Could someone give us some help? >> Thanks, >> Sebastian >> > >
