Hi Mark,
Thank you very much, you are right. It was wrong hosts/ip in /etc/hosts. As
result - connection timeout to these hosts.
Best regards,
Sergey
2013/10/23 Mark Phillips
> Hi Sergey,
>
> This looks like the initial tcp connection is timing out when riak@de5
> and riak@de6 are first tryin
Hi Sergey,
This looks like the initial tcp connection is timing out when riak@de5
and riak@de6 are first trying to talk to the handoff/ip port for
riak@de2 (which would be configured by in riak@de2's app.config).
You may have already gotten to the bottom of why that's happening, but
the first thi
Hi all
What to do in case of loss of the primary partitions !?
6 node cluster, leveldb, 1.3.2
5-6 nodes always waiting to handoff 46 partitions
'riak@de6' waiting to handoff 46 partitions
'riak@de5' waiting to handoff 46 partitions
Active Transfers:
transfer type: hinted_handoff
vnode type: r
No that's the only error. It may be that there were older errors which rolled
out but I would expect a rolling restart would result in at least new errors
but no. It's been 30 hours or so since the restart and still the same output
from riak-admin transfers
I guess I might be able to stop all
Anthony,
The primary partition warning suggests that a vnode that should be
running on your node is not running. After a restart, all primary
vnodes are started, which is why the primary warning goes away.
However, the fact that the warning re-appears is unexpected. The
handoff receiver errors als
Hi,
I have a 12 node riak cluster running riak 0.14.2. I had several nodes
crash with OOM errors, and after restarting them I see the following when
running riak-admin transfers
Attempting to restart script through sudo -u riak
'riak@10.5.11.39' waiting to handoff 1 partitions
'riak@10.5.11.39
