Hi, 64 is a bit low, I guess 128 would be better to avoid such situation.
I. On Thu, Nov 1, 2018 at 2:26 PM Travis Kirstine < tkirst...@firstbasesolutions.com> wrote: > I’m running riak (v2.14) in a 5 node cluster and for some reason one of > the nodes has higher disk usage than the other nodes. The problem seems to > be related to how riak distributes the partitions, in my case I’m using the > default 64, riak has given each node 12 partition except one node that gets > 16 (4x12+16=64). As a result the node with 16 partitions has filled the > disk and become ‘un-reachable’. > > > > I have a node on standby with roughly the same disk space as the failed > node, my concern is that if a add it to the cluster it will overflow as > well. > > > > How do I recover the failed node and add a new node without destroying the > cluster….. BTW just to make things more fun the new node is at a newer > version of riak so I need to perform a rolling upgrade at the same time. > > > > Any help would be greatly appreciated! > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > -- the sun shines for all
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
