Just remember if you are not running AAE, you will want to do a manual repair
on that partition, in order to ensure you have adequate replication:
https://docs.riak.com/riak/kv/2.2.3/using/repair-recovery/repairs.1.html#repairing-partitions
> On Sep 4, 2019, at 5:19 AM, Bryan Hunt
> wrote:
>
Bryan* (misspelled your name), need a morning coffee :(
On 04/09/2019 10:29, Guido Medina wrote:
Thanks a lot Brian, I have deleted such directory and now the node
started, let's see how it behaves.
Guido.
On 04/09/2019 10:19, Bryan Hunt wrote:
Easiest solution is to just delete the vnode -
Thanks a lot Brian, I have deleted such directory and now the node
started, let's see how it behaves.
Guido.
On 04/09/2019 10:19, Bryan Hunt wrote:
Easiest solution is to just delete the vnode - and let it recover from
replicas - vnode directory will be
Easiest solution is to just delete the vnode - and let it recover from replicas
- vnode directory will be 844930634081928249586505293914101120738586001408
> On 4 Sep 2019, at 10:01, Guido Medina wrote:
>
> Hi all,
>
> We had a power cut which caused one of the nodes to corrupt one of the
>
Hi all,
We had a power cut which caused one of the nodes to corrupt one of the
LevelDB files, after this that node doesn't even want to start, here is
the error we are seeing:
2019-09-04 08:46:41.584 [error] <0.2329.0>@riak_kv_vnode:init:527
Failed to start riak_kv_eleveldb_backend backend
